The pdffsck command checks a HiRDB file system area for integrity errors and repairs any errors that are detected. If an inconsistency is detected, the command displays the corresponding file or area.

You should execute the pdffsck command when either of the following occurs:

• The KFPI21586-W message is displayed during execution of the pdfls command
• The available space in the HiRDB file system area becomes less than the original capacity (for example, 100 gigabytes were allocated, but only 80 gigabytes are now available)

The following table describes the integrity check items and repair methods:

Superuser or HiRDB administrator

(a) -c

Specifies that the HiRDB file system area is to be checked only. When the -c option is specified, the HiRDB file system area is not repaired.

(a) HiRDB-file-system-area-name ~<path name> ((up to 165 characters))

Specifies the name of the HiRDB file system area.

1. When you specify the -c option, you can execute the pdffsck command whether or not HiRDB is active. When you omit the -c option, you must execute the pdffsck command as explained below, depending on the purpose of the HiRDB file system area:
   
   • When -k HiRDB-file-system-area-for-DB is specified
     Execute the command after placing all RDAREAs in the HiRDB file system area in command shutdown and closed status with the pdhold -c command, and then terminating the active processes with the pdpfresh command. After executing the pdffsck command, release all RDAREAs from shutdown status with the pdrels command.
     
   • When -k HiRDB-file-system-area-for-SYS is specified
     Execute the command after swapping system log files with the pdlogswap command and then closing the system log file with the pdlogcls command. After executing the pdffsck command, use the pdlogopen command to make the system log file available for use in the active HiRDB.
     
   • When -k HiRDB-file-system-area-for-UTL is specified
     If the HiRDB file system area is being used by a utility, execute the command only after the utility's processing has been completed.
     
   • When -k HiRDB-file-system-area-for-WORK is specified
     Since the HiRDB file system area cannot be restored during operation of HiRDB, execute it after HiRDB has terminated.
     
2. You can execute the pdffsck command with the -c option specified on a HiRDB file system area that is being accessed by another process or user. The pdffsck command with the -c option omitted cannot be executed on a HiRDB file system area that is being accessed by another process or user.
3. The pdffsck command must be executed at each server machine where the HiRDB file system area is stored.
4. If you are executing the command on a HiRDB file system area for which -k SDB has been specified, execute it from the server machine where the updatable back-end server is located.

1. If an I/O error occurs, the command cancels the processing.
2. You can use the pdfls command to check the HiRDB files that have been created in the target HiRDB file system area.
3. If a HiRDB file system area is checked while the RDAREA automatic extension facility is being used, automatic extension occurs after the check processing has terminated. To determine whether or not the RDAREA automatic extension facility is in effect for the target HiRDB file system area, execute the pdfstatfs command.
4. While the pdffsck command is executing, do not execute pdmod or pdrstr. If they are executed, the database may become corrupted.
5. If file repair processing by the pdffsck command is cancelled while it is underway, re-execute the command to complete the repair processing.
6. In HiRDB version 07-02 or earlier, the pdffsck command may not be able to repair information in the management area that has become corrupted. In such a case, the KFPI21585-E message is displayed. As directed in this message, restore the target HiRDB file system area from a backup. For details, see the manual HiRDB Version 9 System Operation Guide.

When the KFPI21559-W message is displayed due to an inconsistency detected in the area, the applicable information item listed below is displayed, as appropriate for the detected inconsistency. If the KFPI21558-I message is displayed but no inconsistency was detected, the information below is not displayed.

(a) When there are unusable HiRDB files (cancellation of file creation or deletion processing)

An unusable HiRDB file is distinguished by the status of the area allocated to it, in terms of whether or not the area itself is usable. If the area is not usable, the command displays the name, start location, and size of every file in the area. Because the area may not be unusable for all the unusable files, the displayed unusable file count may not match the number of files that are listed.

 
unusable file count                 aa...a
file list
     FILE NAME                  OFFSET[kB]    SIZE[kB]
     bb...b                        cc...c      dd...d
       :                              :           :
total unusable area size[kB]             ee...e
 

Explanation

aa...a

Number of unusable HiRDB files (1 to 4 decimal digits)

bb...b

Name of a HiRDB file whose area is not usable (up to 30 characters)

cc...c

Offset to the start of the HiRDB file (up to 10 decimal digits)

dd...d

Size of the HiRDB file (kilobytes) (up to 10 decimal digits)

ee...e

Total size (kilobytes) of all the HiRDB files whose area is not usable (the size that can be reused as free area by repairing) (up to 10 decimal digits)

(b) When there are unusable areas (cancellation of file extension processing)

The start location and size of each unusable area is displayed. This information is displayed for all applicable areas. The displayed unusable area count always matches the number of areas that are listed.

 
unusable area count                aa...a
area list
     OFFSET[kB]                      SIZE[kB]
     bb...b                           cc...c
       :                                 :
total unusable area size[kB]          dd...d
 

Explanation

aa...a

Number of unusable areas (up to 4 decimal digits)

bb...b

Offset to the start of an unusable area (up to 10 decimal digits)

cc...c

Size of the unusable area (kilobytes) (up to 10 decimal digits)

dd...d

Total size (kilobytes) of all the areas that are unusable (the size that can be reused as free area by repairing) (up to 10 decimal digits)

(c) When there are both unusable HiRDB files and unusable areas

 
unusable file count                 aa...a
file list
     FILE NAME                  OFFSET[kB]    SIZE[kB]
     bb...b                        cc...c      dd...d
       :                              :           :
unusable area count                ff...f
area list
     OFFSET[kB]                     SIZE[kB]
     gg...g                          hh...h
       :                                :
total unusable area size[kB]         ee...e
 

Explanation

aa...a

Number of unusable HiRDB files (1 to 4 decimal digits)

bb...b

Name of a HiRDB file whose area is not usable (up to 30 characters)

cc...c

Offset to the start of the HiRDB file (up to 10 decimal digits)

dd...d

Size of the HiRDB file (kilobytes) (up to 10 decimal digits)

ee...e

Total size (kilobytes) of all HiRDB files whose area is not usable and of the unusable areas (the size that can be reused as free area by repairing) (up to 10 decimal digits)

ff...f

Number of unusable areas (up to 4 decimal digits)

gg...g

Offset to the start of an unusable area (up to 10 decimal digits)

hh...h

Size of an unusable area (kilobytes) (up to 10 decimal digits)