Kbase P2124: Error 888 on startup of database after a power failure.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/15/2008 |
|
Status: Verified
SYMPTOM(s):
** Those dates don't match, so you have the wrong copy of one of them. (888)
Error 888 displayed attempting to start database
Unable to start database
Power failure has occurred that caused system to emergency shut down
CAUSE:
A power cut caused the dbname.bi and dbname.db time stamps to become out of sync with each other.
FIX:
1. Truncate the before image file (bi).
Syntax: proutil dbname -C truncate BI
2. If truncation of the before image file fails restore from the previous backup and, - whenever is possible, roll forward the after image files.
If the backup file is not a feasible option, see the notes below.
IMPORTANT NOTE:
The -F option is provided as a last resort emergency measure and should never be needed. This parameter is made available to allow you to extract and salvage as much data as possible from a database that is damaged and otherwise unusable. It should be used only when the alternative is loss of the entire database. It cannot be stressed strongly enough that using ?F must be considered as the very last resource. Going back to a backup is the safest option.
Forcing into the database will compromise the physical and logical integrity of your database. To force into the database truncate the Before Image file with -F parameter.
Syntax: proutil -C truncate bi -F
Once you use the (-F) option to open your database, the database is marked as damaged with the following message:
"You must Dump and Load the Database to regain integrity."
Now the database must be dumped and reloaded into a brand new database.