Salesforce

PROSTRCT unlock extents causes 1124 when accessing the database file that it replaces

Printable View
« Go Back

Information

 
TitlePROSTRCT unlock extents causes 1124 when accessing the database file that it replaces
URL NameP77515
Article Number000150668
EnvironmentProduct: Progress
Version: 9.1C, 9.1D
OS: All supported platforms
Question/Problem Description
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
Steps to Reproduce
Clarifying Information
Error MessageSYSTEM 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)
Defect NumberDefect OE00099678 / 20040106-008
Enhancement Number
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 Progress 9.1C, 9.1D, the block headers (block 1) of the re-created extents are not initialized correctly. Attempts to access these blocks then cause a SYSTEM ERROR when reading the block as can be seen in the above messages.
Resolution
This issue has been fixed in Progress 9.1D09 and later. Upgrade to this Service Pack level or higher to obtain the fix.
Workaround
If upgrading is not possible, and reverting to backup really is not possible, revert to the pre-PROSTRCT UNLOCK EXTENTS baseline/backup and use the method described in Article:
Notes
Keyword Phrase
Last Modified Date11/20/2020 7:38 AM
Powered by