Kbase P93673: Last transaction id differs from the production database to the hot standby database
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/30/2004 |
|
Status: Unverified
SYMPTOM(s):
Last transaction id differs from the production database to the hot standby database
Production database is shutdown to perform an offline backup
During the shutdown of the production database a single user connection queries the -DBStatus-LastTran VST
The previous backup is restored and all the after image files are rolled forwards
A single user session queries the LastTran of the standby database
The _DBStatus-LastTran is different on production and standby database
CAUSE:
This is the expected behavior. There is a mapping between transaction id's and transaction table entry numbers. If the transaction table entry corresponding to the next transaction id is in use (for some other previous transaction id), then that transaction id is skipped.
FIX:
To ensure the production database and the hot backup are in sync for roll forward recovery, use the return code of the roll forward command.
There is no VST's that can determine this.