Kbase P7510: How to recover from a missing or lost BI file on a version 8.x database.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/03/2009 |
|
Status: Verified
GOAL:
How to recover from a missing or lost BI file on a version 8.x database.
FACT(s) (Environment):
Progress 8.x
FIX:
This solution is designed to assist database administrators with recovery from a user or system error that results in the corruption or loss of a before-image (BI) file.
Remember that if crash recovery is not possible because of a damaged BI file the Progress number one recommendation is always to restore a valid backup.
Hardware problems and operating system bugs often occur without notification. If the database happens to have a corrupted or missing BI file as a result of one of these unforeseen scenarios and you cannot go to a backup, take the following steps as one way to address the problem.
The following also holds true in the case of user error when operating system backups fail to list all components for the database and you do not have the correct BI file when you restore from a backup.
General errors that indicates you are missing a BI file or are pointing to an inappropriate BI file are:
The following applies to Progress version 8 databases:
If you use a single volume database, skip Step 1 and proceed directly to step 2.
1) PROSTRCT unlock dbname (causes new empty BI extents to be created).
2) Try to access the database in single user mode.
You might receive the following error:
Invalid BI file, before-image file is zero length. (877)
3) If the session started with any error, you must force into your database. This can be done with the following command:
proutil dbname -C truncate bi -FYou should schedule a dump & load at your earliest convenience