Salesforce

roll forward fails 1024 8999 1046 1048

« Go Back

Information

 
Titleroll forward fails 1024 8999 1046 1048
URL Nameroll-forward-fails-1024-8999-1046-1048
Article Number000126529
EnvironmentProduct: Progress
Version: 8.x, 9.x
Product: OpenEdge
Version: 10.x, 11.x
OS: Windows
Question/Problem Description
Ai file fails to complete roll forward with errors 1024 8999 1046 1048

stack trace from _dbutil.exe
rldumpchain2
rlStructDump
rlaiGetNextNote
dsaAIGetNextNote
StgMakeUniqueName
Steps to Reproduce
Clarifying Information
Some notes are processed before roll forward fails.

rfutil -C aimage scan verbose displays error 9333 in the header of the output against a truncated ai file
 
Incomplete ai file detected, expected <n>, got <n-x>. 
Subsequent roll forwards will fail unless this situation is resolved. 
See extended help on this error for further information. (9333)

rfutil -C aimage scan verbose does not show footer information in the trailer of the output against a very large ai file. The following trailer information are missing:
 
<n> notes were processed. (1634)
<n> in-flight transactions. (3785)
<n> transactions were started. (1635)
<n> transactions were completed. (11138)
At the end of the .ai file, <n> transactions were still active. (1636)
Error MessageSYSTEM ERROR: Rollforward Apply AI note, BKUPDCTR=<number>, note updctr=<number>. (1028)
area <n>, dbkey <block>, record type <ai file record> (8999)
SYSTEM ERROR: Roll forward of file <file name> did not complete normally (1046)
SYSTEM ERROR: End of last note read is at file offset <ai file offset> (1048)
Defect Number
Enhancement Number
Cause
This ai file is not the complete ai file, which is why it get's "so-far" processing ai transaction notes then fails at an ai file offset.
Resolution
1. Determine where the ai file-copy failed, then roll forward with the "roll foward retry" option.

 Assuming this ai file still available at it's original location: 
  • Compare the filezsizes and use checksum or similar to verify
    For example, from a Windows Powershell console, compare the resulting SHA256 HASH output at both locations
    C:\ powershell "Get-FileHash <full directory path>\<aifile>
  • If these don't match,
    • Review the file transfer methods. Somewhere in the transfer of this ai file from it's origin to the current location, it's become corrupt/truncated. Once the complete ai file is available, use "rfutil -C roll forward retry".
  • If these do match:
    • There's likely a hardware or memory problem on this roll-forward machine. Unless this can be resolved, migrate to a new server and run the roll forward operations from there.
    • If they do match because there was no file transfer between the archived copy and the roll forward, but the roll forward is from a mapped drive, it's likely the ai file was unable to be read for the duration of the roll forward or the size of the ai file is restricted by quotas. Once corrected at the OS levels,  use "rfutil -C roll forward retry"
    • The file transfer method itself can introduce corruption. For this reason, compressing (gzip, tar) the ai files to transfer is recommended.

2. If the AI Archiver (AIMGT) is not used to manage ai files, but RFUTIL scripts instead:

Before this AI file was marked EMPTY (rfutil -C aimage empty), the OS copy either:
  • Copied the ai file before it was FULL, or 
  • Failed to copy the complete FULL ai file
Since the ai file was incomplete at source, the best option is to use a later PROBKUP of this database, or to take a new one, and roll forward from there.

Otherwise, if the source (Crashed) database is still available, but inaccessible, another option would be to force in with "proutil -C truncate bi -F" then do a full ASCII (not binary) dump and load.  Once loaded, you'd need to run application specific back-end reports to ensure logical application integrity (for example, orphan parent, child records like order numbers and order lines, or workflow like deliveries without invoices)
Workaround
Notes
Keyword Phrase
Last Modified Date11/20/2020 7:08 AM

Powered by