Kbase P146781: Cannot forward ai files against a restore that was dumped and loaded
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/22/2009 |
|
Status: Unverified
SYMPTOM(s):
Rolling forward ai files
Rolling forward after image files
Restored backup was dumped and loaded
Dump and load before rolling forward
**Cannot find or open file <>, error = 2 (43)
Expected ai file number <X> but file specified is <Y> in sequence. (8019)
** The database was last changed <date/time>. (831)
** The after-image file expected <date/time>. (832)
** Those dates don't match, so you have the wrong copy of one of them. (833)
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
CAUSE:
The transaction log records that are in the ai journals are mostly operations that depend on the physical locations of records and index entries. When you dump and load, all the rowids change and the ai records are matched up to the target database by rowids and block numbers. Since they are different in the source and target, they can't be applied. It is not just the ai sequence numbers that are wrong. The contents of the ai files are wrong too. They don't contain enough information to do a logical rollforward against a different database.
FIX:
This is an expected result as the restored backup should not be dumped and loaded before rolling forward after image files.