Kbase P131873: roll forward fails with error 8019 on first aiarchived backup sequence number
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/18/2010 |
|
Status: Verified
SYMPTOM(s):
The first aiarchived extent with the new backup sequence number change fails to roll forward
restoring all extents with the same database backup sequence number
Expected ai file number n but file specified is n-1 in sequence. (8019)
** Those dates don't match, so you have the wrong copy of one of them. (833)
roll forward open \aiarc\ais1\D!~101B~WRK~aiarc~dbname.20080728.101732.00005.00000007.dbname.a2 error: -1. (11014)
FACT(s) (Environment):
ai files are named by the ai archiver daemon process
ai files are referenced in the dbname.archival.log
OpenEdge 10.1X
All Supported Operating Systems
CAUSE:
The switch to the new extent happens after the master block in the database has been updated with the new database backup sequence number. The first extent with the new backup sequence number is actually the last ai extent for the previous backup sequence number. This issue affects both online and offline probkups.
FIX:
Roll forward the next named ai extent with the new backup sequence number.
For example:
The aiarchiver log file extract below, shows:
-> an aiarchiver daemon switch pre backup
-> an aiarchiver daemon switch resulting from a full online probkup
-> an aiarchiver daemon switch (post full online probkup)
[dbname.archival.log]
0001,D:\101C\WRK\aiarc\dbname,20080728,102808,20080728,101732,4,6,D:\101C\WRK\aiarc\dbname.a1,D:\101C\WRK\aiarc\ais1,D:\101C\WRK\aiarc\ais1\D!~101C~WRK~aiarc~dbname.20080728.101732.00004.00000006.dbname.a1
0032,D:\101C\WRK\aiarc\dbname,20080728,102940,1,5,20080728,102939,8,1,dbnamenl2.bak,BACKUP_SET_20080728_102939
0001,D:\101C\WRK\aiarc\dbname,20080728,102943,20080728,101732,5,7,D:\101C\WRK\aiarc\dbname.a2,D:\101C\WRK\aiarc\ais1,D:\101C\WRK\aiarc\ais1\D!~101C~WRK~aiarc~dbname.20080728.101732.00005.00000007.dbname.a2
The resulting named ai files in the ai archiver directory at the time (-aiarcdir) are:
directory~database.dateAIFMstarted.timeAIFMstarted.backup-sequence.ai-sequence.extent-name
D!~101B~WRK~aiarc~dbname.20080728.101732.00004.00000006.dbname.a1
D!~101B~WRK~aiarc~dbname.20080728.101732.00005.00000007.dbname.a2 << should be named (...)00004.00000007.dbname.a2
D!~101B~WRK~aiarc~dbname.20080728.101732.00005.00000008.dbname.a3
If we were to roll foward (..)00005.00000007.dbname.a2 against the online probkup we took, it would fail. This ai file 'belongs' as the last ai file to the previous bakup sequence '00004'.
Instead, rollfoward the aifile named with the new backup sequence +1. In the above example - this would be (...).00005.00000008.dbname.a3