Salesforce

What to do when an After Image file is corrupted.

« Go Back

Information

 
TitleWhat to do when an After Image file is corrupted.
URL NameP14008
Article Number000140008
EnvironmentProduct: OpenEdge
Version: 10.x
OS: All supported platforms
Question/Problem Description
After Image file corrupted by Operating System Crash
Steps to Reproduce
Clarifying Information
Error MessageUnable to read extent header, ret = <return-value> file = <file-name>. (6109)

Extent <dbname>.a has the wrong creation date <timestamp is not sensible like 1970 1999> (9212)

SYSTEM ERROR: ai header corrupt, blk 0, reason 1, addr (3644)

This is not a Progress ai file (756)
AI file cannot be used with this database. (508)
Defect Number
Enhancement Number
Cause
Resolution
1. Copy all remaining non-corrupt after image files to a safe location, if needed. The corrupt ai files are irrecoverable.
$  rfutil <dbname> -C aimage list
Will report usually the same ai corruption error messages on ai files that are irrecoverable

2. Disable After Imaging
$  rfutil <dbname> -C aimage end

3. Remove all ai files then add them back to the database structure. It is imperative that AI files are removed.
$   prostrct remove <dbname> -a
$   prostrct add <dbname> addai.st

3. Backup the database or mark it as backed up (a valid backup can be taken later online for roll forward processing)
$  rfutil <dbname> -C mark backedup

4. Re-Enable After Imaging
$  rfutil <dbname> -C aimage begin

The re-enabling of the after image process will format all ai files and should correct the AI file corruption.

Alternatively, since OpenEdge 10.1B AI can be enabled online with an online probkup:
$   probkup online <dbname> <backup volume> enableai enableaiarchiver -aiarcdir

For further information refer to Article  How to enable or disable after imaging (AI) online 

In some conditions the corruption of the ai file will not allow you to disable after-imaging.
In that event, after you have copied the AI files to a safe location.
  • Rename the corrupt after image files to a different name.
  • Copy one of the good AI files to the name of the bad AI file.
  • Then again attempt to disable after imaging.
Workaround
Notes
Keyword Phrase
Last Modified Date11/20/2020 7:00 AM

Powered by