Kbase P26329: Return Code shows success when rolling forward partial ai file
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
21/01/2009 |
|
Status: Verified
SYMPTOM(s):
Rolling forward AI files via a script and receive errors indicating that a file cannot be roll forwarded.
Receive 1028 errors when starting the database
Receive 1028 errors when rolling forward AI files against a database
SYSTEM ERROR: Physical redo, BKUPDCTR=<number>, note updctr=<number>. (1028)
SYSTEM ERROR: Physical redo, BKUPDCTR=21481, note updctr=21558. (1028)
area , dbkey , record type (8999)
area 15, dbkey 1380768, record type 43 (8999)
SYSTEM ERROR: Roll forward of file <filename> did not complete normally (1046)
SYSTEM ERROR: End of last note read is at file offset (1048)
Incomplete ai file detected, expected <blocks>, got <blocks>.
Subsequent roll forwards will fail unless this situation is resolved.
See extended help on this error for further information. (9333)
FACT(s) (Environment):
Return codes for previous commands return success.
All Supported Operating Systems
Progress/OpenEdge Product Family
CAUSE:
Enhancement Request# OE00090159
CAUSE:
Return Code shows success when rolling forward partial ai file. Return code is correct because rfutil process did roll forward all transactions found in a partial AI file.
FIX:
Need to validate that the AI file was successfully archived prior to emptying AI file for reuse.
The Enhancement Request# OE00090159 was made in OpenEdge 10.0A that changes the return code to something other than 0 or 2 to indicate that the file is a partial AI file. This allows DBAs to identify probable backup / archive problems when rolling forward offending AI file, rather than waiting for subsequent roll forward processes to experience failures.