Kbase P182665: proutil dbname -C dbanalys gets 210 error when doing the block analysis portion for the Schema Area
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/7/2011 |
|
Status: Unverified
SYMPTOM(s):
proutil dbname -C dbanalys gets 210 error when doing the block analysis portion for the Schema Area
SYSTEM ERROR: Attempt to read block <number> which does not exist. (210)
dbrpr also found bad fragments.
idxfix against the database shows the following errors:
SYSTEM ERROR: Index <index-num> (<owner-name>.<table-name>, <index-name>) contains <entry-count> entries, but <record-count> records found. (8779)
SYSTEM ERROR: Index <index-num> (<owner-name>.<table-name>, <index-name>) contains 6350 entries, but 6349 records found. (8779)
SYSTEM ERROR: Index fix found 6 errors. (4974)
Index fix made 49 index changes. (4975)
Second idxfix on this database shows original 8779 errors mentioned earlier.
dbtool option 3 showed many errors similar to the following:
There were 1 error(s) found in 2506830 of tablename(151).
Number of fields mismatch. Expected 16, got 17
Record format errors found: 899
dbtool option 4 showed many errors similar to:
Number of fields mismatch. Expected 4, got 15
dbtool option 4 showed:
Record format errors found: 1798
idxbuild fails with the following errors:
Index Rebuild Utility
=====================
Select one of the following:
All - Rebuild all the indexes
Some - Rebuild only some of the indexes
Quit - Quit, do not rebuild
Enter your selection:
all
ERROR - dsmRecordGet of _field failed. -1
ERROR - dsmRecordGet of _index-field failed. -1
ERROR - dsmRecordGet of _index-field failed. -1
ERROR - dsmRecordGet of _index-field failed. -1
ERROR - dsmRecordGet of _field failed. -1
ERROR - dsmRecordGet of _index-field failed. -1
Do you have enough disk space for index sorting? (y
)
y
(But the idxbuild process does not start after this).
Last good backup of the database is not an option as the backup is too old and many records have been added since it was taken.
Binary dump and load of the database did not address the corruption.
FACT(s) (Environment):
Windows
Progress 9.1D
Progress 9.1D Patch 09
CAUSE:
MetaSchema corruption.
FIX:
Perform an ASCII dump and load of the database to address corruption.