Kbase P77515: prostrct unlock extents causes 1124 when accessing the database file that it replaces
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/17/2006 |
|
Status: Verified
SYMPTOM(s):
prostrct unlock extents causes 1124 when accessing the database file that it replaces
prostrct unlock -extents to recover missing extents
idxbuild fails with error 1124 after database file is replaced
proutil truncate bi fails with error 1124 after database file is replaced
SYSTEM ERROR: wrong dbkey in block. Found <dbkey>, should be <dbkey2> (1124)
SYSTEM ERROR: read wrong dbkey at offset 2048 in file <file> found 32,
expected 64, retrying. (9445)
Corrupt block detected when reading from database. (4229)
bkRead: Error occurred in area <mum>, block number: 1, extent: <name>. (10560)
Writing block 1 to log file. Please save and send the log file to Progress
Software Corp. for investigation. (10561)
CAUSE:
Bug# 20040106-008
CAUSE:
When a database extent is removed, renamed or somehow lost, the "prostrct unlock dbname -extents" utility may be used to create a replacement (empty) extent in order to restore the physical integrity of the database. In version 9, the block headers (block 1) of the re-created extents are not initialized correctly. Attempts to access these blocks then cause a system error as can be seen in the above messages.
FIX:
This issue has been fixed in Progress 9.1D09 and later. Upgrade to this service pack level or higher to obtain the fix.