When an error occurs, the HiRDB administrator must take the following actions:

1. Check the output messages and the manual HiRDB Version 9 Messages to determine the causes of the error.
2. Execute the pdinfoget command to acquire the troubleshooting information output to $PDDIR/spool and $PDDIR/tmp. The pdinfoget command outputs the initial information file, which summarizes the information needed to identify the cause of the error, and the detailed information file, which summarizes the information necessary for detailed investigation after the cause of the error is identified.

Remarks

• The information you need in order to use the support service to correct errors is summarized in Appendix C. Information Needed for Troubleshooting. In the event of a problem, we recommend strongly that the HiRDB administrator always refer to Appendix C. Information Needed for Troubleshooting.
• Frequently asked questions about the error handling procedures are answered in Q&A format in A.4 Errors.

Executing the pdinfoget command collects a backup of the troubleshooting information under the directory of the server machine on which the pdinfoget command was executed.

Before you can execute the pdinfoget command, the PDDIR and PDCONFPATH environment variables must be set up. Make sure that they are set up.

Execute the pdinfoget command by following the procedure described below.

Procedure

1. Check whether the server machine on which you plan to execute the pdinfoget command has sufficient disk space for storing the troubleshooting information. You can use the pdinfoget -m command to estimate the amount of space needed for the error information to be acquired.
2. On the server machine on which you plan to execute the pdinfoget command, create a directory for storing troubleshooting information.^#
3. Execute the pdinfoget command. Specify the directory prepared in step 2 for the option of the pdinfoget command.
4. When the troubleshooting information is no longer needed, use the pdcspool command to delete it. Keeping it will cause a disk space shortage.

#

If a directory already exists, check whether the directories listed below exist under that directory. If they exist, an error will occur when the pdinfoget command is executed.

Output destination directory	Directories that cause an error if they are located under the output destination directory
Initial information file output destination directory	CLTDIR PDDIR spool conf .dbenv pdistup OSFILE SYSLOG COREINF
Detailed information file output destination directory	PDDIR spool tmp CLTDIR

If the directories listed in the table above exist, take one of the following actions, and then re-execute the command:

• Specify a different directory for the initial information file output destination directory or the detailed information file output destination directory.
• If the information in the specified directory is not needed, delete it all.

When a server process or client is terminated forcibly, HiRDB outputs troubleshooting information to the $PDDIR/spool directory. In addition, whenever the Ctrl + C keys are pressed to terminate a command or a utility while it is executing, the command or utility outputs a temporary work file to the $PDDIR/tmp directory, where it remains resident. If these troubleshooting and temporary work files are left on the disk, they might stress the capacity of the disk on which the HiRDB directory resides. A shortage of free space on the disk containing the HiRDB directory can cause HiRDB to terminate abnormally. To avoid such a problem, HiRDB deletes the following files periodically:

• Troubleshooting information files (files in the $PDDIR/spool directory)
• Temporary work files (files in the $PDDIR/tmp directory)

Normally, HiRDB deletes these files every 24 hours. You can change this deletion interval in the pd_spool_cleanup_interval operand. You can also specify that only files that were output a specified number of days previous to the current date are to be deleted; you make this specification in the pd_spool_cleanup_interval_level operand.

You can also use the following methods to all delete troubleshooting information (files in the $PDDIR/spool directory):

• You can use the pdcspool command to delete troubleshooting information files. You can also use this command to delete temporary work files (files in the $PDDIR/tmp directory).
• You can configure HiRDB to delete troubleshooting information files automatically when it starts. You use the pd_spool_cleanup operand to specify whether troubleshooting information files are to be deleted automatically. If this operand is omitted, the files are deleted. You can also use the pd_spool_cleanup_level operand to specify that only troubleshooting information files that were output a specified number of days previous to the current date are to be deleted.
  

  Reference note

  To select the troubleshooting information that is to be deleted, you can specify a pdcspool command option, or you can specify a value in the pd_spool_cleanup_level or pd_spool_cleanup_interval_level operand.

  Note

  In some cases, troubleshooting information files that are output by commands or utilities executed by users other than the HiRDB administrator are not deleted. In these cases, a user with the privilege of deleting troubleshooting information files must delete the files with a command such as the OS's rm command.

You can specify the following operands to reduce the amount of troubleshooting information that is output. Specify these operands as needed.

• pd_cancel_dump: Specifies whether troubleshooting information is to be output.
• pd_client_waittime_over_abort: Specifies whether troubleshooting information is to be output when a client that is executing a transaction exceeds its maximum wait time (value specified in the PDCWAITTIME operand of the client environment definitions).
• pd_clt_waittime_over_dump_level: Specifies whether to limit the units for which the shared memory dump is to be output when the client's maximum wait time (the value of the PDCWAITTIME operand in the client environment definition) is exceeded.
• pd_debug_info_netstat: Specifies whether network information is to be output as part of the troubleshooting information that is collected when a server process or HiRDB (unit) terminates abnormally.
• pd_dump_suppress_watch_time: Specifies a period of time during which re-output of troubleshooting information is to be suppressed.