Kbase P4395: Database crashes with error 43 and error 210
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/2/2004 |
|
Status: Verified
SYMPTOM(s):
Database is down
Error: ** Cannot find or open file <file-name>, errno = <number>. (43)
SYSTEM ERROR: Attempt to read block <number> which does not exist. (210)
SYSTEM ERROR: wrong dbkey in block. Found <dbkey>, should be <dbkey2> (1124)
Database performs crash recovery on startup
Database crashes again with similar error messages once users start running the application
CAUSE:
Error 210 indicates corruption in a database block, this message usually is followed by an error 1124 which details the block that was found instead. These events trigger a core file and the associated protrace file should be analyzed by Progress Technical Support to help establish the cause.
Error 43 indicates problem while trying to access the file referenced in the message, usually the file with the damaged block or some temporary file. IN this case it is a consequence of the previous errors.
FIX:
It is strongly recommended to restore your most recent backup, otherwise the damaged blocks can be removed with the undocumented dbrpr utility. This will result in data loss and will need to be followed up by a dump and load to restore database integrity. Please refer to Progress Solution 2077, "How to Run dbscan With Database Repair Utility (dbrpr)" to determine where the database has corruption. Please call Technical Support for assistance with recovering the database. Restoring from backup may still be necessary.