Kbase P21864: Truncation of bi file on hot backup indicates no in-flight transactions, yet 1 transaction is backed
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/23/2010 |
|
Status: Verified
SYMPTOM(s):
Truncation of bi file on hot backup indicates no in-flight transactions, yet 1 transaction is backed out.
Inconsistency between in-flight transactions and number of transactions backed out when truncating of bi file on hot backup.
proutil -C truncate bi session begin for root on batch (451)
Begin Physical Undo 1 transaction at block <xxxx> offset <xxxx> (7163)
Begin Logical Undo Phase, incomplete transactions are being backed out. (7162)
Begin Logical Undo Phase, 1 incomplete transactions are being backed out (7162)
FACT(s) (Environment):
Progress 9.1D
UNIX
CHANGE:
Automated truncation of before image file on target / hot stand by database
CAUSE:
Bug# OE00087880
CAUSE:
Roll forward in-flight count was inconsistent with values of "undoable" transactions during crash recovery.
FIX:
Upgrade to 9.1D07 or later.
Upgrade to 10.0A or later.
A change was made so that in-flight calculation for the number of active transactions for roll forward is now based off the transaction table.