Appendix C. Information Needed for Troubleshooting

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.CategoryCollected informationCollection methodPrf.NRAT
1OSsyslogfileUse an operating system function (command).111
2CPU utilization and device statusUse the OS's sar command. For details about this command, see the documentation for the operating system.343
3CPU activity or memory status for the processUse the OS's top command. For details about this command, see the documentation for the operating system.343
4Virtual memory informationUse the OS's vmstat command. For details about this command, see the documentation for the operating system.343
5Network status informationUse the OS's netstat command. For details about this command, see the documentation for the operating system.343
6HiRDBHiRDB error informationUse the pdgeter command. Save the output information onto a medium such as a DAT.222
7Error log filesError log files are output to the directory $PDDIR/spool/errlog.222
8Command log fileCommand log files are output to the directory $PDDIR/spool/cmdlog.222
9HiRDB system definition informationSave files in the directory $PDDIR/conf on a medium such as a DAT.454
10Table and index definition informationSave files describing definition SQL used when defining tables or indexes on a medium such as a DAT.4[Figure][Figure]
11Statistical informationUse the statistical information output start and end commands (pdstbegin and pdstend) to collect the information listed below:
  • Statistical information on system operations (sys)
    Recommended interval: 1 hour
  • Statistical information on the global buffer pool (buf)
  • Statistical information for HiRDB files on database manipulation (fil)
This information is output to the directories $PDDIR/spool/pdstj1 and pdstj2.
After collecting the statistical information, use the statistics analysis utility (pdstedit command) to edit the statistical information.
6[Figure][Figure]
12Server communication control informationUse 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.
  • Recommended collection interval: 60 seconds
  • Disk space needed to collect information one time: approximately 62 KB.
544
13Information on the status of server transactionsUse 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.
  • Recommended collection interval: 60 seconds
  • Disk space needed to collect information one time: approximately 30 KB
565
14Information on the status of server processesUse 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.
  • Recommended collection interval: 60 seconds
  • Disk space needed to collect information one time: approximately 28 KB
565
15Information on server lockUse 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.
  • Recommended collection interval: 60 seconds
  • Disk space needed to collect information one time: approximately 62 KB
5[Figure][Figure]
16Information on the global buffer usage statusUse 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.
  • Recommended collection interval: 60 seconds
  • Disk space needed to collect information one time: approximately 3 KB
5[Figure][Figure]
17SQL trace files and error log filesSQL 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.
[Figure]65
18System log filesUse pdlogunld to unload the system log. Save the unload log files on a medium such as a DAT.676
19Core filesIf a utility stops responding, use the following procedure to collect the core files:
Procedure
  1. Use the pdls -d prc command to check the server process ID of the utility.
  2. Use the pdcancel -d command to cancel the process checked in step 1.
[Figure]3[Figure]
Legend:
Prf.: Performance problem
NR: No-response
AT: Abnormal termination
[Figure]: Collection of this information is not necessary.
Notes
  • The necessary disk space is a reference value. The actual value will depend on the system configuration.
  • Available disk space is suppressed because files that can be added to by redirecting output information increase in size incrementally. Therefore, create a general-purpose shell script that swaps files and reuses them in a specific generation.