Kbase P13250: Errors 831,832,833,9215,9213,1486,605 trying to roll forward an after image file
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/15/2010 |
|
Status: Verified
SYMPTOM(s):
Rolling forward after image file gives errors
** The database was last changed <date/time>. (831)
** The database was last changed Sun Jan 5 22:11:49 2003. (831)
** The after-image file expected <date 2>. (832)
** The after-image file expected Mon Jan 6 02:20:35 2003. (832)
** Those dates don't match, so you have the wrong copy of one of them. (833)
Last open date mismatch. (9215)
Extent <ai-name.an> has a different last opened date <date>, (9213)
Database is damaged, see documentation. (1486)
Probable backup/restore error. (605)
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
CAUSE:
Trying to roll forward the wrong AI file.
FIX:
To determine what date and time an AI file was opened for output, use the aimage scan option to rfutil.
Command:
rfutil dbname -C aimage scan -a <pathname of AI file>
Example of output:
PROGRESS Version 9.1D02 as of Sun Oct 27 21:07:25 EST 2002
After-image dates for this after-image file: (1633)
Last AIMAGE BEGIN Mon Jan 6 04:07:44 2003 (1640)
This file was last opened for output on Mon Jan 6 04:07:55 2003. (1643)
2447430 notes were processed. (1634)
0 in-flight transactions. (3785)
270769 transactions were started. (1635)
At the end of the .AI file, 0 transactions were still active. (1636)
File last opened date and time needs to be consistent with expected date and time reported in 832 error. If these dates and time do not match, there is no way to force the application of the AI file against that database.
Another way to identify which AI file you should apply can be determined by reviewing log file of database where AI file was originally produced. The original database log should contain date and time information associated with the backup and then AI files created once aimage session begin command was issued.