Kbase P124744: rmDOChange error when applying AI file to warm standby database
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/5/2007 |
|
Status: Unverified
SYMPTOM(s):
rmDOChange error when applying AI file to warm standby database
Database logfile:
RFUTIL 0: rfutil -C roll forward session begin for root on batch. (451)
RFUTIL 0: Begin Physical Redo Phase at 9216 . (5326)
RFUTIL 0: rmDoChange: old record 689988887 area 12 updctr 181 has size 12336 expected 80 in txn 279399429 updctr 181
RFUTIL 0: ** Save file named core for analysis by Progress Software Corporation. (439)
RFUTIL 0: rfutil -C roll forward session end. (334)
Core dumped
PROGRESS stack trace as of
Command line arguments are /progress/Ver91.D05/bin/_rfutil <dbname> -C roll forward -a <AI file>
(1) uttrace() +0xe0 from: /progress/Ver91.D05/bin/_rfutil
(2) utcore() +0xd8 from: /progress/Ver91.D05/bin/_rfutil
(3) drexit() +0x52c from: /progress/Ver91.D05/bin/_rfutil
(4) msgout() +0x2d0 from: /progress/Ver91.D05/bin/_rfutil
(5) msgdCB() +0x2c from: /progress/Ver91.D05/bin/_rfutil
(6) msgCB() +0x44 from: /progress/Ver91.D05/bin/_rfutil
(7) dsmMsgdCallBack() +0xa8 from: /progress/Ver91.D05/bin/_rfutil
(8) rmDoChange() +0xa8 from: /progress/Ver91.D05/bin/_rfutil
(9) rlredo() +0x6ac from: /progress/Ver91.D05/bin/_rfutil
(10) dorollf() +0x684 from: /progress/Ver91.D05/bin/_rfutil
(11) warmstrt() +0x70 from: /progress/Ver91.D05/bin/_rfutil
(12) rlseto() +0x410 from: /progress/Ver91.D05/bin/_rfutil
(13) dbSetOpen() +0x498 from: /progress/Ver91.D05/bin/_rfutil
(14) drrfutil() +0x1d8 from: /progress/Ver91.D05/bin/_rfutil
(15) main() +0x11c from: /progress/Ver91.D05/bin/_rfutil
(16) _start() +0xb8 from: /progress/Ver91.D05/bin/_rfutil
The same AI file applied to a second warm spare database does not fail
CAUSE:
Inspection of Operating System logs shows that a disc failure had occurred which corrupted the warm standby database.
FIX:
Restore a backup of the source database and roll forward the AI files to that database or use the other warm spare database as a new source database.