Kbase P137214: Index corruption after binary load
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/18/2009 |
|
Status: Unverified
SYMPTOM(s):
Index corruption after binary load
Report got incorrect number of records after a fresh dump/loaded database
FOR EACH failed to find some record records using equality match in the WHERE clause
Get error " index could not be deleted" trying delete those records
SYSTEM ERROR: Index <index name> in <table> for recid <recid> could not be deleted. (1422)
Fails to find records from specific table just after binary dump/load.
Error 8783 running idxcheck
SYSTEM ERROR: Index<index-num> (<owner-name>.<table-name>, <index-name>): couldn't find key <key> recid <DBKEY>. (8783)
FACT(s) (Environment):
Data Dictionary dump/load works fine
Database has been just dump and loaded
Used Binary dump and load
FOR EACH finds records sucessfuly using "larger than" in the WHERE clause
Results from dbanalys match number or records and number of indexes
HP-UX 11.11
PA-RISC 64-bit
OpenEdge 10.1B03 Service Pack
CAUSE:
Bug# OE00178231
FIX:
As a workaround, use Data Dictionary to dump and load the table.