Kbase P90295: rmUndoLogicalChange failure after Emergency shutdown
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/04/2011 |
|
Status: Verified
SYMPTOM(s):
Cannot truncate the database before image file
Database was shutdown via an Emergency Shutdown.
Fails going through logical undo phase of crash recovery
rmUndoLogicalChange: recid <RECID> area <Areanum> txn <Transnum> updctr <n>
rmFetchRecord returns <n1> expected <n2>
Stack trace from _progres reads:
rmUndoLogicalChange
rlundo
rllbk
warmstrt
FACT(s) (Environment):
All Supported Operating Systems
Progress 8.x
Progress 9.x
OpenEdge 10.x
OpenEdge Category: Database
CAUSE:
Forced shutdown (proshut -F) immediately suspends all writes to the database. The immediate suspension of writes can prevent BI notes which begin in a prior block from being completely recorded thus leaving only a partial note and consequently preventing crash recovery.
FIX:
Restore database from a backup. If using After Image files, restore the database from backup and then roll forward ai files.
If restoring the database from a backup is not possible, then force truncate the BI file to bypass crash recovery. For additional information regarding the Perils of Forcing into a database, please reference solution: P24330, "Consequences of using the -F startup option"
Command: proutil dbname -C truncate bi -F