When the pdgeter command is executed, a backup copy of the troubleshooting information is created under a directory in the server machine where the pdgeter command was entered. Any directory can be specified in an option of the pdgeter command. The backup copy can also be created at any device, not just in the server machine used to enter the pdgeter command (not supported in the AIX 5L version). The following is the procedure for executing the pdgeter command:
- Procedure
- Check that the server machine where the pdgeter command is entered has sufficient disk space to store the troubleshooting information.
- Create a directory* for storing the troubleshooting information at the server machine where the pdgeter command is entered. This step is not necessary if the troubleshooting information is to be output to a device.
- If troubleshooting information for a machine other than the server machine where the pdgeter command is entered is to be output to a device, a work directory is required. In such a case, create a work directory* in the server machine where the pdgeter command is entered.
- Copy the pdinit control statement to $PDDIR/conf, using INITCONT as the file name. If all troubleshooting information is to be obtained (by specifying the -a option), copy the information under the file name INITCONT into $PDDIR/conf at the server machine where the pdgeter command is entered.
- Copy the pdmod control statement into $PDDIR/conf. In this case, any file name can be used.
- If shared memory is to be dumped (by omitting the -m option from the pdgeter command), check that there is a directory for storing a shared memory dump ($PDDIR/spool/pdshmdump) at the server machine subject to collection of troubleshooting information (the server machine with the host name specified in the -x option of the pdgeter command). If there is no such directory, create it.
- Execute the pdgeter command. Specify the directories provided in steps 2 and 3 in the pdgeter command's options.
- When the troubleshooting information is no longer needed, delete it with the pdcspool command (retaining it may result in a shortage of disk space).
- * If this directory already exists, check whether or not it contains any of the directories or files listed below; if it contains these directories or files, the pdgeter command will result in an error.
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 may 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 or not troubleshooting information files are to be deleted automatically. The default value for this operand is that these files are deleted automatically. 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.