Kbase P45306: Error (4521) when accessing a single volume database after f
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/2/2003 |
|
Status: Unverified
FACT(s) (Environment):
Progress 8.x
SYMPTOM(s):
SYSTEM ERROR: Invalid blocksize <blocksize> in database <dbname>. (4521)
SYSTEM ERROR: Invalid blocksize -8225 in database dbname.db (4521)
SYSTEM ERROR: bkaddr called with negative blkaddr: -16843011 (762)
Single volume database
Cannot access database
Cannot force into the database
Cannot access database -RO
prowin32 sysdb -RO generates: Errors (1552) (1152) (4229) then GPF on prowin32
WARNING: Before-image file of database <name> is not truncated. (1552)
SYSTEM ERROR: read wrong dbkey at offset <offset> in file dbname.db found <dbkey>, expected <dbkey>, retrying. (1152)
Corrupt block detected when reading from database. (4229)
No backup
No current .df
CAUSE:
File System got corrupt which can be seen in the log file, where the block that is being pointed to is from another file than it should be, or the block being pointed to in the database is from another file and the log file is merely reporting the garbage.
Investigation of the database proved that the schema was corrupted and as a consequence, the whole database because the schema corruption makes it quite impossible to DUMP the data.
Although we MAY have managed to recover the master block to some readable state, with the schema gone, the information that helps Progress make some sense of all the binary mess in a data block is gone.
Verdict: unrecoverable database.
FIX:
The File System is not reliable. Before proceding further, take an OS backup of the database to another set of disks, then check these disks and remake the filesystem.
The database is unrecoverable and will have to be rebuilt from paper records.