Kbase P20739: Before Image (.bi) corrupt or missing and database can't sta
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/1/2004 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.x
SYMPTOM(s):
Before Image (.bi) corrupt or missing and database can't start
.b1 is lost, missing or damaged
bi file is lost, missing or damaged
Cannot start database when the .b1 file cannot be used
Cannot start database when the .b1 file time stamp does not match
Cannot find or open file database.bi errno = 2. (43)
SYSTEM ERROR: The before-image file has the wrong cluster size. (881)
** The database was last used <date/time>. (886)
** The before-image file expected <date/time>. (887)
** Those dates don't match, so you have the wrong copy of one of them. (888)
CAUSE:
This scenario is usually a result of hardware problems and/or operating system bugs that impact the database integrity without forewarning. It can also be a consequence of user error during OS backups, when failing to list all related components correctly for the database, or when using automated scripts and commands are executing in the background - there is not enough time between commands for the previous command to finish. For example: truncating the bi while the database is still shutting down, resulting in the incorrect OS copy of the bi file when you restore from a backup. Whatever the initial cause, a combination of these error messages will result and indicate that the cause of failure is that the .bi file is lost, corrupted or is pointing to an inappropriate bi file at startup.
FIX:
Progress recommends that the customer should always go to backup in these circumstances. If the database structure has been altered since last known dbname.st, then going to last fully verified backup should be the ONLY course of action.