Kbase P24282: SYSTEM ERROR: End of last note read is at file offset (1048) when rolling forward an After Image fil
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/3/2010 |
|
Status: Verified
SYMPTOM(s):
Roll forward of after image extent fails with errors (1028)
SYSTEM ERROR: Rollforward Apply AI note, BKUPDCTR=<number>, note updctr=<number>. (1028)
area , dbkey , record type (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)
User 0 died with 1 buffers locked. (2523)
rfutil -C roll forward session end. (334)
Script copies the after image files to a backup system using RPC commands.
After image file that failed to roll forward is the same size on the backup system as in production
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
CAUSE:
Performing a Cksum against the after image file that failed and the one that worked shows a CRC calculation discrepancy.
Due was determined to be a Network issue. During the copy of the original After Image file the network dropped some of the file information.
FIX:
1. FTP the file from production to backup and perform a cksum against the After Image file on production and the backup system. If the production and backup systems are the same files roll this file forward.
Added a cksum command to the Roll Forward Script. If the cksum of the after image file on Production does not match the cksum of the after image file on the Warm Spare the after image file is not rolled forward.
Troubleshoot the network and/or hardware problems that caused the difference in the cksum calculation.