Kbase P15161: 10611 Error when starting database in multi-user mode after running conv89 with either 9.1D01 or 9.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/17/2011 |
|
Status: Verified
SYMPTOM(s):
Database won't start
Errors starting database in multi-user mode.
conv89 utility was used to convert the database.
updatevst utility was run after the conv89.
Protrace file contains the following function call: rlVerifyTxTable()
SYSTEM ERROR: rlVerifyTxTable mb_txnSequence: note=0 mstrblk=0. (10611)
SYSTEM ERROR: The broker is exiting unexpectedly, beginning Abnormal Shutdown. (5292)
FACT(s) (Environment):
Progress 9.1D
All Supported Operating Systems
CHANGE:
Applied 9.1D01 or 9.1D02
CAUSE:
Bug # 20021128-033
CAUSE:
Known Issue. One of the .bi notes, INMEM, was changed beginning with 9.1D01.
The conv89 utility in 9.1D01 and 9.1D02 uses 9.1D FCS mkschema. The mkschema portion of the conv89 will generate bi notes. These bi notes may, by chance, include the INMEM note and it's still in 91DFCS format. Everything is fine including updatevst. The database will crash when started because the crash recovery mechanism expects that all the notes from conv89 should be in 91D02 format. The error happens here, but the cause is that 9.1D01/9.1D02 conv89 was using 91D FCS mkschema.
If Service Pack 9.1D01 or 9.1D02 is installed, and a conv89 command is issued to convert a Progress 8.x database to Progress 9.x database, the database may be left in a corrupt state. An error occurs when the database is started for the first time in multi-user mode after the conv89. The error indicates a transaction sequence mismatch. Recovery is possible only by restoring a backup.
FIX:
Upgrade to 9.1D03 or higher.