Kbase P21968: Opening of standby database can cause next AI roll forward to fail.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
08/09/2005 |
|
Status: Unverified
SYMPTOM(s):
After Image fails to roll forward on standby database with errors 831 and 832
** Those dates don't match, so you have the wrong copy of one of them. (833)
At the end of the .ai file, <number> transactions were still active. (1636)
** The database was last changed <date/time>. (831)
** The after-image file expected <date/time>. (832)
CAUSE:
The standby database was opened while active transactions were propagated to this database during the previous AI roll forward session (system error 1636). The Standby database cannot be opened by any utility because the date and time stamps of the database files will be updated and will not not match the date and time stamp the After Image file expects. Utilities that open the database and the cause the database to go through crash recovery are Progress clients, proutil commands such as truncating the bi file, and starting the broker.
Any utlity/process which opens the database will cause the database to go through crash recovery
FIX:
Restore the database from backup and roll forward all Ai files up until the point where the database was opened. There is no way to recover from this. Do not open the standby database in an AI replication configuration.