In HiRDB version 07-02 and earlier, if file creation, deletion, or extension processing is canceled, some area might fall into a status that belongs neither to unmanageable files nor to unreferenceable areas. This is the area of corrupted management information and corrupted file caused by operations such as a duplicate allocation of area; this occurrence has adverse effects on system operation. The following illustrates the concept of duplicate allocation:

Because the area management information is corrupted, any attempt to recover the corrupted target file results in corruption of other files. If you upgrade the system in this status, the corrupted area will be inherited.

Note

• When area management information becomes corrupted, the pdfbkup, pdfrstr, pdcopy, and pdrstr commands cannot recover the information.
• The pdffsck command can detect corruption of area management information, but cannot repair it. In such a case, the command displays the KFPI21585-E message and terminates abnormally.

Re-create all HiRDB file system areas. Then take the action described below for each HiRDB file system area purpose (-k option value in the pdfmkfs command).

(a) For DB and SDB

Recover the database from its backup. This backup must contain the RDAREAs that were stored in the HiRDB file system area before the area management information was corrupted.

(b) For SYS

Create the system log files, synchronization point dump files, and status files. Note that the system cannot be restarted because the system files required for restart cannot be provided. Perform a normal start.

If the security audit facility is used, create the audit trail file and then restart the HiRDB and security audit facility.

(c) For WORK

No action is needed because work tables are created automatically by HiRDB during SQL execution.

(d) For UTL

Because the backup file for the pdcopy command and the unload data files for the pdrorg command have been lost, re-execute the pdcopy or pdrorg command, if necessary.