Kbase 17243: Recovering From A Hole In The Database: Error 4524
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/12/2009 |
|
Status: Unverified
GOAL:
How to recover from a hole in your database, error 4524.
SYMPTOM(s):
SYSTEM ERROR: File <file-name> too small <length>, blocksize <blocksize> extend failed." (4524)
Error 4524 occurs when trying to access a database after it has been corrupted or the proutil session died or was disconnected.
FACT(s) (Environment):
Progress 8.x
CAUSE:
When listing the database directory (or where the bi files are), the file described in the error message is smaller in size than the blocksize expected.
FIX:
Progress Software recommends always to restore from backup first. This should be done to maintain data integrity. If this cannot be done, try the following:
1) Delete the bi file reported in the error.
For example: rm dbname.b2
2) prostrct unlock dbname
If you are missing any database files when you run PROSTRCT UNLOCK,
PROSTRCT automatically replaces the missing extents with an empty
extent.
3) Then try to truncate the bi file , for example:
proutil dbname -C truncate bi -biblocksize 8192
4) If you still encounter the error, delete the bi file again (from
step 1), create an empty database, and rename the bi file from the
empty database to the file name described in the error message.
Then truncate the bi file with the -F option. This will force the
access into the database. Progress recommends a dump/load of the
database whenever you use the -F option.