DP4 System error 87. Origin: Database corruption
Database corruption type %1 in table nr %2
Your database is corrupt. You need to restore a back up and apply log files, or (if you do not have a back up) you can try running REORGDB -CORRUPT, provided DBCHECK does not report errors when checking the data file.
Non-recoverable.
Two numbers are displayed with this error. The first number indicates the type of corruption found. The second error is usually a record type number or length. The meaning of the various possible numbers is as follows:
| Number | Meaning |
|---|---|
| 2 | An index node has an invalid length, (or possibly a pointer to an index node was corrupt). Index node lengths should be between 4 and 500. The length found is displayed. If the number appears to be valid then it is not the node length that is invalid, but the length of the record containing the node. |
| 3 | An index node in the list of free nodes has a bad length. The length found is displayed. Either the record length of the node is bad, or the node length is not 4, indicating that the node is not in fact free. This error could arise in older versions of DP4 after a DBRECOV. |
| 4 | A linked list entry points to a record with an illegal length or the wrong type number. The type number found is displayed. Linked lists are only used when non unique primary keys are used. This feature is no longer offically supported so this error should never arise in practice. |
| 5 | An index entry points to a record with an illegal length or the wrong type number, indicating that either the data file is corrupted or that the index contains a corrupt entry.
The type number of the record that was expected is displayed. See How to Find a Table, Field or Role Name from a Number shown in a System Error Message to find out how to obtain further information about which table is causing the problem. |
| 8 | When reusing an area in the data file that should contain a hole, either the hole length was wrong or the type number was non zero indicating the record is not actually a hole. The type number found is displayed. This error could arise in older versions of DP4 after a DBRECOV. |
| 6,7,9 | Hash area corrupt. These errors could only occur if hashed indexing, which is no longer supported, is selected. |
| 10 | An index node contains inconsistent data. |
| 11 | The database header (at the start of the index file) is corrupt. |
| 12 | An index record contains a corrupted key. |