Kbase P102604: prorest fails during Logical Undo Phase
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
04/04/2005 |
|
Status: Unverified
SYMPTOM(s):
prorest fails during Logical Undo Phase
Begin Logical Undo Phase, incomplete transactions are being backed out. (7162)
SYSTEM ERROR: read wrong dbkey at offset <offset> in file <file> found <dbkey>, expected <dbkey>, retrying. (9445)
Corrupt block detected when reading from database. (4229)
<func-name>: Error occurred in area <num>, block number: <num>, extent<name>: . (10560)
SYSTEM ERROR: wrong dbkey in block. Found 0, should be <dbkey2> (1124)
file in 9445 message is not a bi file
Block buffer dump shows an empty block
4th byte offset in Block buffer dump is 07
truncate bi session also fails during the Logical Undo phase
CAUSE:
There are issues with the initial probkup online, or in the file transfer of this backup. The prorest is then an incomplete restore of the online probkup - the database manager restores all the data that it has in the probkup. When the bi file then performs the Logical Undo Phase for open transaction(s) as recorded in the bi notes, the database manager needs to reference a block to undo an entry in a record which it was supposed to find in a block that was not restored; in other words, a block in the restored database that is ABOVE the high water mark, an empty block.
FIX:
Investigate the source of this issue as detailed below:
Steps:
1.) Ensure that the backup location has not run out of diskspace and is preferably local to the same machine/ filesystem that the database is housed.
2.) Manually re-baseline the probkup online:
$ probkup online dbname dbname.bak
3.) Check for errors reported during this process.
3a) If errors are reported, there are block corruption in the source database that need to be addressed.
3b) If no errors are reported, then check the resulting probkup file:
$ prorest dbname dbname.bak -vp
4.) Transfer the probkup file to where it needs restoring, checking that there are no issues with the transfer. The md5 freeware utility is very useful to this end. Otherwise us a compresser utilitiy such as winzip at source and then unzip once they're copied to the target directory across the network drives.