Kbase P61656: Roll forward with no integrity fails with Error 4554 after a failed roll forward
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
24/03/2011 |
|
Status: Verified
SYMPTOM(s):
Roll forward with no integrity fails with Error 4554 after a failed roll forward
rlaiextrd: Transaction table mismatch ptran: note . (4554)
Previous roll forward failed due to applying the wrong ai file error 8019
Expected ai file number <X> but file specified is <Y> in sequence. (8019)
FACT(s) (Environment):
Rolling forward with no integrity option '-i' to improve the roll forward process
rfutil ${DATABASE} -C roll forward -i -B 10000 -a ${AI_TMP}
All Supported Operating Systems
Progress/OpenEdge Product Family
CAUSE:
The option "-i" is for NO CRASH PROTECTION. If you run with the -i parameter and the operation fails for any reason, the database cannot go through crash recovery.
FIX:
Rebaseline the roll forward database environment by restoring the most recent verified probkup and applying subsequent ai notes.
Do not use the option "-i" unless there are 100% checks that the expected After-Image sequence is being applied or you are prepared to rebaseline the roll forward database environment when roll forward failure occurs for whatever reason. Note that using the no integrity flag also negates the possibility of using the 'rfutil -C roll forward retry' functionality.