Kbase 19017: A way to Recover From Error 4524 with all 8.x Versions
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/15/2008 |
|
Status: Unverified
FACT(s) (Environment):
Progress 8.x
SYMPTOM(s):
SYSTEM ERROR: File <file-name> too small <length>, blocksize <blocksize> extend failed." (4524)
<File-name> in the 4524 error message refers to a before-image extent
No valid backup available
CAUSE:
This error indicates a corruption in the before-image file (BI).
FIX:
If crash recovery is not possible because of a damaged BI file, we strongly recommend restoring a valid backup. There is no integrity guarantee otherwise. Please refer to Solution P43320 regarding the consequences of undertaking the following.
STEPS:
1.) Since the trigger of the error is the check for the BI blocksize, a possible solution is to provide a BI extent with the correct blocksize. This can be done by copying a BI extent which is still okay to the file the 4524 error message refers.
For example:
$ cp msports.b1 msports.b2
2.) You can create another multivolume database with the needed BI blocksize and copy the BI extent to the missing extent file.
For example:
$ cp test.b1 msports.b2
3.) After you have done steps 1 or 2, you will need to force access into the database:
proutil msports -C truncate bi -F
You will be able to access the database now, but bear in mind that it is in an inconsistent state. The logical integrity of the database will need to be examined.