Kbase 21935: Error: "Find Failed on Index 1033 error -1215"
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
05/06/2002 |
|
SUMMARY:
Find Failed on index 1033 error -1215
This is an error message you might receive when doing an idxfix or idxbvuild against a database. The message is informational and does not indicate any corruption or pose a threat to the database.
EXPLANATION:
This really is not an error message, but rather an informational message. The message implies that the database or indexes are corrupted in some manner.
The message normally appears when you start the appropriate index administration utility (idxcheck, idxfix, or idxbuild). But again, the message is not truly an error. Also, it is not part of the calculation represented at the end of an idxbuild process with regards to number of errors encountered during the idxbuild process.
Example:
PROGRESS PATCH Version 9.1C09 as of December 19, 2001
The BI file is being automatically truncated. (1526)
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:
Find Failed on index 1033 error -1215
Do you have enough disk space for index sorting? (y
)
Details of indexes being deactivated ...
Followed by Phase I output ...
Sorting and building of indexes for groups ...
Index rebuild status and sort file information ...
Index activation information ...
Index rebuild complete. 0 error(s) encountered. (1644)
The message is the result of our utility internally traversing index numbers within a range of defined index numbers (independent of index entries within the _index table). The message might be displayed when finding an index number that is not currently defined within the database. This is the case for databases that do not have SQL tables / indexes defined. However, if "Both" or "SQL" was selected when the Progress installation was done, the appearance of this message would not be expected behavior.
The message has been reported against some databases when an idxfix , option 6: Delete one record and it's index entries was performed against a database.
Progress is investigating the cause of this message on databases where SQL-92 is supported. The problem with the informational message is that it does not provide sufficient information to associate which index number could be in question. Rather the message reports index 1033 which is a meta table: _Index-Number. This is being addressed, such that future Progress releases will report what index number was identified as not being supported or defined.
Note: If you are experiencing this message and your database supports 4GL and SQL clients or SQL only clients, then you may want to take a closer look at your database. You could have Meta Schema corruption. In one customers case, it was only the index rebuild which showed this error. Database scanned clean and dbanalys also showed no problems. The customer went to create an incremental .df between two databases. He expected only 1 change in the incremental.df. The incremental.df showed more than 1 change. He then took a closer look at his output from dbanalys and determined that they were missing some fields from one of the tables.