20.2 Collecting tuning information from the system log

Executor: HiRDB administrator
Organization of this section
(1) Tuning information that can be collected from the system log
(2) Tuning information collection procedure

(1) Tuning information that can be collected from the system log

Table 20-5 shows the tuning information that can be collected from the system log.

Table 20-5 Tuning information that can be collected from the system log

Type of statistical informationExplanation
Index statistical informationidxOutputs information related to index page splits from within the index statistical information.
CONNECT/DISCONNECT statistical information*cncOutputs (to a DAT file only) statistical information on CONNECTs and DISCONNECTs.

* In the case of a HiRDB/Parallel Server, this statistical information is output to the front-end server's system log file.

(2) Tuning information collection procedure

Figure 20-4 shows the procedure for collecting tuning information (collecting tuning information from the system log).

Figure 20-4 Procedure for collecting tuning information (collecting tuning information from the system log)

[Figure]

Explanation
  1. HiRDB collects system log information in system log files.
  2. Use the pdlogunld command to unload system log files and create unload log files.
    When unload log files are output to multiple server machines in a HiRDB/Parallel Server, the OS's rcp command (remote copy) or NFS (network file system) can be used to collect the unload log files.
    System log information can also be read directly by the statistics analysis utility. For details on the statistics analysis utility, see the manual HiRDB Version 8 Command Reference.
  3. Execute the statistics analysis utility using the created unload log files as the input information. You can then use the execution results to tune HiRDB or UAPs.