If an error occurs on both versions of the current file, information needed to restart HiRDB (unit) is lost and HiRDB can no longer be restarted. In such a case, the pdstart dbdestroy command must be used to start HiRDB forcibly.

When HiRDB is restarted in this manner, it does not inherit information that was in effect during the previous session. Therefore, the HiRDB administrator must recover the database by executing the database recovery utility using a backup copy and the system log (unload log) as the input information. For details on the database recovery utility, see 21. Database Recovery Procedures.

Before executing forced startup of HiRDB, see 1.6.2 Notes on forced startup of HiRDB (or a unit).

Note

• The database should be placed in inaccessible status (by placing the corresponding RDAREAs in command shutdown and closed status with the pdhold -c command) until the database has been recovered.
• When HiRDB is started forcibly, all RDAREAs (including system RDAREAs) that were updated during the previous HiRDB session are destroyed. These RDAREAs must be recovered with the database recovery utility. If they are not recovered, subsequent HiRDB operations cannot be guaranteed.