The information needed for troubleshooting can be divided broadly into operating system information and HiRDB information. Operating system information is collected using operating system commands. HiRDB information is collected using HiRDB commands.
If you use problem-solving support or Q&A support services, the information explained in Table C-1 may be needed. Table C-1 explains the information needed for troubleshooting. The priority for collecting information is divided into three categories: a performance problem, a no-response, and abnormal termination. There are seven priority levels, with 1 being the highest priority and 7 being the lowest.
Table C-1 Information needed for troubleshooting
No. | Category | Collected information | Collection method | Prf. | NR | AT |
---|---|---|---|---|---|---|
1 | OS | syslogfile | Use an operating system function (command). | 1 | 1 | 1 |
2 | CPU utilization and device status | Use the OS's sar command. For details about this command, see the documentation for the operating system. | 3 | 4 | 3 | |
3 | CPU activity or memory status for the process | Use the OS's top command. For details about this command, see the documentation for the operating system. | 3 | 4 | 3 | |
4 | Virtual memory information | Use the OS's vmstat command. For details about this command, see the documentation for the operating system. | 3 | 4 | 3 | |
5 | Network status information | Use the OS's netstat command. For details about this command, see the documentation for the operating system. | 3 | 4 | 3 | |
6 | HiRDB | HiRDB error information | Use the pdgeter command. Save the output information onto a medium such as a DAT. | 2 | 2 | 2 |
7 | Error log files | Error log files are output to the directory $PDDIR/spool/errlog. | 2 | 2 | 2 | |
8 | Command log file | Command log files are output to the directory $PDDIR/spool/cmdlog. | 2 | 2 | 2 | |
9 | HiRDB system definition information | Save files in the directory $PDDIR/conf on a medium such as a DAT. | 4 | 5 | 4 | |
10 | Table and index definition information | Save files describing definition SQL used when defining tables or indexes on a medium such as a DAT. | 4 | ![]() | ![]() | |
11 | Statistical information | Use the statistical information output start and end commands (pdstbegin and pdstend) to collect the information listed below:
After collecting the statistical information, use the statistics analysis utility (pdstedit command) to edit the statistical information. | 6 | ![]() | ![]() | |
12 | Server communication control information | Use the pdls -d rpc -a command. Execute this command at 60-second intervals and output to the target file using an appending redirect (>>). Save this file on a medium such as a DAT.
| 5 | 4 | 4 | |
13 | Information on the status of server transactions | Use the pdls -d tm -a command. Execute this command at 60-second intervals and output to the target file using an appending redirect (>>). Save this file on a medium such as a DAT.
| 5 | 6 | 5 | |
14 | Information on the status of server processes | Use the pdls -d prc -a command. Execute this command at 60-second intervals and output to the target file using an appending redirect (>>). Save this file on a medium such as a DAT.
| 5 | 6 | 5 | |
15 | Information on server lock | Use the pdls -d lck -a command. Execute this command at 60-second intervals and output to the target file using an appending redirect (>>). Save this file on a medium such as a DAT.
| 5 | ![]() | ![]() | |
16 | Information on the global buffer usage status | Use the pdbufls command. Execute this command at 60-second intervals and output to the target file using an appending redirect (>>). Save this file on a medium such as a DAT.
| 5 | ![]() | ![]() | |
17 | SQL trace files and error log files | SQL trace files and error log files are output to the directory specified by the PDCLTPATH operand of the client environment definition. When the PDCLTPATH operand is omitted, these files are output to the directory in which the AP is currently running. Save the output files on a medium such as a DAT. File names start with pderr or pdsql. | ![]() | 6 | 5 | |
18 | System log files | Use pdlogunld to unload the system log. Save the unload log files on a medium such as a DAT. | 6 | 7 | 6 | |
19 | Core files | If a utility stops responding, use the following procedure to collect the core files: Procedure
| ![]() | 3 | ![]() |