With databases, inconsistencies can occur between extents from accidental misuse of operating system copy utilities or from incorrectly administered backup and restore procedures. The database engine synchronizes opening and updating the DB, BI, and AI extents to ensure the consistency of the database. If the engine finds an inconsistency among these extents, it returns an error message and stops any attempt to open the database. If this happens, try to restore the database from backups. As a last resort, you can use the PROSTRCT utility with the UNLOCK qualifier to open the database to dump the data. Use PROSTRCT UNLOCK only as a last resort. The locked database might not unlock, or the resulting unlocked database might be damaged and invalid.
To unlock a damaged database:
1. Unlock the database with PROSTRCT UNLOCK.
The syntax is as follows:
prostrct unlock db-name
Note: If you are missing any database extents when you run PROSTRCT UNLOCK, PROSTRCT replaces any missing extents with empty formatted extents and displays a message. You can determine whether this has occurred the next time any utility or program tries to open the database.
2. Use the Data Administration tool if you are using a graphical interface or the Data Dictionary if you are using a character interface to dump the data definitions and the table contents.
3. Exit the database.
4. Create a new void database.
5. Restart the database and reload the dumped data definitions and data into the new database.
