The pdinfoget command acquires error information when a failure occurs in the HiRDB system in order to determine the cause of the failure. It can also be used to estimate the amount of information to be acquired.
HiRDB administrator who is authorized to reference information files output by HiRDB as well as OS information files
pdinfoget -e initial-information-file-output-directory-name |
pdinfoget -m |
Specifies the absolute path name of an existing directory to which the initial information file (containing information needed to determine the cause of a failure) is to be output. The maximum length of a directory name is as follows.
If the specified directory does not exist or the write privilege for it has not been granted, the command outputs an error message and cancels processing.
The command outputs the initial information file and the execution log to the specified initial information file output directory. The initial information file is an archive file that consists of multiple files. The names of the files are formatted as shown below:
For details about the error information that is collected in the initial information file, see Table 2-8.
Specifies the absolute path name of an existing directory to which the detail information file (containing information needed for further investigation after the cause of an error has been determined) is to be output. The maximum length of a directory name is as follows:
If the specified directory does not exist or the write privilege for it has not been granted, the command outputs an error message and cancels processing.
The detail information file is an archive file that consists of multiple files. The names of the files are formatted as shown below:
For details about the error information that is collected in the detail information file, see Table 2-8.
After acquiring error information, the pdinfoget command archives or compresses the error information by executing a HiRDB or OS command. This option specifies the absolute path name of an existing directory that is to be used to store temporary work files. The maximum length of a directory name is as follows:
If the specified directory does not exist or the write privilege for it has not been granted, the command outputs an error message and cancels processing.
The command creates work directory pdinfoget_work_date-and-time under the specified directory and then stores work files in that directory. If there is already a directory named pdinfoget_work_date-and-time, the command terminates with an error.
Estimate the file capacity beforehand and allocate a sufficient amount of disk space. The following shows the estimation formula:
If this option is omitted, the following directory is assumed:
-w option | pd_tmp_directory operand in system definition | ||
---|---|---|---|
Specified | Omitted | ||
TMP environment variable# | |||
Specified | Omitted | ||
Specified | Directory specified in the -w option | ||
Omitted | Directory specified in pd_tmp_directory | Directory specified in TMP | %PDDIR%\tmp directory |
If this option is omitted, the temporary files created when the error information is archived or compressed are stored in the directory shown in the table below. In this table, 1 indicates the highest priority for the output destination directory:
Processing | Output directory | File name |
---|---|---|
Archiving |
| AFI* |
Compression |
| cab* |
These files are deleted when the processing terminates.
Note that if an error occurs during the processing, the files might not be deleted. If this happens, delete the files manually.
Specifies the absolute path name of the event-log-file that is set to be acquired by default by the pdinfoget command. If you specify event log files, specify the event logs that have been saved to a file by a program such as Event Viewer.
By default, the pdinfoget command acquires the following event log files to which event logs existing when the pdinfoget command is executed are backed up:
You might need to use the -s option to acquire a file in the following case:
Specifies the absolute path name of a Dr. Watson log file that is to be acquired as initial information.
If this option is omitted, Dr. Watson logs are not acquired.
Specifies the absolute path name of a crash dump file that is to be acquired as detail information.
If this option is omitted, a crash dump files is not acquired.
This option is related to memory databases. Normally, you must not specify this option.
Specifies the absolute path name of an existing directory to which an XDS shared memory dump file is to be output. If this option is omitted, an XDS shared memory dump file is not acquired. The maximum length of a directory name is as follows:
If the specified directory does not exist or the write privilege for it has not been granted, the command outputs an error message and cancels processing.
For the destination of the XDS shared memory dump file, allocate an amount of space that is at least equal to the value displayed by the -m option as the estimated amount of error information.
If the-m option was not able to provide a value for the estimated amount of error information (because, for example, an error occurred), you must allocate at least twice the sum of the sizes of the database areas for all XDSs in the server machine where the pdinfoget command is executed. For details about estimating the sizes of the database areas for XDSs, see Estimating memory requirements in the HiRDB Version 9 Memory Database Installation and Operation Guide.
Do not specify for the output directory any directory under $PDDIR. If such a directory is specified, HiRDB might terminate abnormally due to a shortage of space.
An XDS shared memory dump file is output when the conditions shown in the table below are satisfied:
Condition | Whether XDS shared memory dump file is output | |
---|---|---|
-b option | XDS status | |
Specified | Running | Output |
Inactive | Output However, if there is no information in the shared memory, the XDS shared memory dump file is not output. |
Specifies that an estimate of the size of the error information to be acquired is to be output. The size estimates are output to the standard output in the following format:
File type | Display format (megabytes) |
---|---|
Initial information file | init_directory = xxx Mbyte |
Detail information file | detail_directory = yyyy Mbyte |
XDS shared memory dump file | dump_directory = zzzz Mbyte# |
Legend: xxx, yyyy, zzzz: Numeric values
If you also specify the -s, -l, or -c option to acquire error information, the estimate includes the size of that error information. For this reason, always specify the -s, -l, or -c option. If an option other than -s, -l, or -c is specified together with -m, the command will terminate with an error.
Table 2-8 List of error information acquired by the pdinfoget command
Information item to be acquired | Whether acquired | Initial information | Detail information | |||
---|---|---|---|---|---|---|
HiRDB command | Information about HiRDB status acquired by executing a HiRDB command | Unit and internal component status | Y | Y | N | |
Server process status | Y | Y | N | |||
HiRDB server's schedule status | Y | Y | N | |||
HiRDB server settings | Y | Y | N | |||
HiRDB server status in unit | Y | Y | N | |||
Information about transaction being executed | Y | Y | N | |||
User identifier information | Y | Y | N | |||
Lock information | Y | Y | N | |||
Lock pool usage status | Y | Y | N | |||
Internal lock information | Y | Y | N | |||
Semaphore information | Y | Y | N | |||
Message queue information | Y | Y | N | |||
Unit and server status | Y | Y | N | |||
Shared memory information | Y | Y | N | |||
HiRDB version information | Y | Y | N | |||
Server process communication control information | Y | Y | N | |||
Global buffer usage information | Y | Y | N | |||
RDAREA status display | Y | Y | N | |||
SQL object information | Y | Y | N | |||
HiRDB setup information | Y | Y | N | |||
System switchover facility information | Y | Y | N | |||
XDS summary error information | Y | Y | N | |||
XDS database status | Y | #3 | N | |||
HiRDB information file | Definition referenced by HiRDB and resulting output file | All directories and files under %PDDIR%\spool | Y | N | Y | |
Files under %PDDIR%\spool | Command log file | Y | Y | N | ||
Message log file | Y | Y | N | |||
Error log file | Y | Y | N | |||
Remote command information file | Y | Y | N | |||
System switchover facility information file | Y | Y | N | |||
Error snap information file | Y | Y | N | |||
Abort information file | Y | Y | N | |||
cwaitover information file | Y | Y | N | |||
System definition information (conf/*, %PDCONFPATH%) | Y | Y | N | |||
Simple setup tool information (pdistup/*) | bin | N | N | N | ||
conf | N | N | N | |||
ini | N | N | N | |||
sample | Y | Y | N | |||
tmp | Y | Y | N | |||
spool | Y | Y | N | |||
pdi_log.txt | Y | Y | N | |||
HiRDB database environment information (%PDDIR%\.dbenv\*) | Y | Y | N | |||
Under HiRDB internal work directory (%PDDIR%\tmp\*) | Y | N | Y | |||
Client trace information (files under %PDCLTPATH%) | SQL trace information | Y | #1 | #1 | ||
Error log file | Y | Y | N | |||
pdess* file | Y | Y | N | |||
UAP statistical information | Y | Y | N | |||
All information about specification difference handling libraries (%PDDIR%\UXPLDIR\*) | Y | N | Y | |||
Files under specification difference handling library information directory | Specification difference handling library error information | Y | Y | N | ||
OS command | Information about OS status acquired by executing a command | Process information | #2 | Y | N | |
Disk information | Y | Y | N | |||
Status of inter-process communication facility | Y | Y | N | |||
CPU usage rate and disk status | #2 | Y | N | |||
Host name | Y | Y | N | |||
IP configuration | Y | Y | N | |||
OS information file | Definition referenced by OS and resulting output file | OS version information | Y | Y | N | |
Machine information | Y | Y | N | |||
Processor information | Y | Y | N | |||
Installed memory information | Y | Y | N | |||
Registry information | Y | Y | N | |||
Environment variable information | Y | Y | N | |||
Network information | Y | Y | N | |||
Event log file | Y | Y | N | |||
Dr. Watson log file | Y | Y | N | |||
Crash dump file | Y | N | Y |
Condition | Whether XDS database status information is acquired | |
---|---|---|
XDS status | System used to execute command | |
Running | Running system | Acquired |
Standby system | Not acquired | |
Inactive | Running system | Not acquired |
Standby system | Not acquired |
Table 2-9 Directories that cause an error if located in an output directory
Output directory | Directories that cause an error if located in the output directory |
---|---|
Output directory for initial information file | CLTDIR PDDIR spool conf .dbenv pdistup uxpldir OSFILE SYSLOG COREINF |
Output directory for detail information file | PDDIR spool tmp uxpldir CLTDIR COREINF |
KFPN10403-I init information file output, file=initial-information-file-path-name |
%ERRORLEVEL% | Termination status | Meaning and action |
---|---|---|
0 | Normal termination | Terminated normally. If the KFPN10451-I message has been issued, archiving or compression of the error information has not been completed.
|
4 | Warning termination |
|
8 | Abnormal termination | Processing was canceled because of an error.
|