Kbase P52050: Is it possible to truncate the bi file on the hot standby?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
23/04/2008 |
|
Status: Verified
GOAL:
Is it possible to truncate the bi file on the hot standby?
GOAL:
Is it possible to truncate the bi before rolling forward AI extents?
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Versions
OpenEdge Fathom Category: Replication
FIX:
Truncating the bi on a hot standby should not be done.
While it is technically possible to truncate the bi file of a hot standby and not invalidate the standby strategy (if the number of Active Transactions were zero), this is not a supported usage and Progress will not guarantee that there are no in-flight transactions when truncating.
If there are in-flight transactions when the truncate is performed, it will invalidate the standby strategy. In which case, if after truncating the bi you did try to roll forward the next extent, you would get time stamp errors like:
** The database was last changed Tue Nov 4 14:38:30 2003. (831)
** The after-image file expected Tue Nov 4 14:31:35 2003. (832)
** Those dates don't match, so you have the wrong copy of one of them. (833)
This is because the database is opened when the bi is truncated. The roll forward qualifier to rfutil will fail if the database is opened before all AI extents are applied.