Nonstop Database, HiRDB Version 9 System Operation Guide

[Contents][Index][Back][Next]

8.6.1 Basics

If a deadlock or timeout occurs when Y is specified for the pd_lck_deadlock_info operand, HiRDB outputs the information shown in the following table.

Table 8-7 Information output when a deadlock or timeout occurs

Output information Description
Deadlock information
  • This is information that is output about a deadlock that has occurred between transactions within a server.
  • For a HiRDB parallel server configuration, a deadlock between servers is reported as timeout information.
  • For more information on deadlock, see the HiRDB Version 9 UAP Development Guide.
Timeout information This is information that indicates that the lock-release wait time has elapsed.
Organization of this subsection
(1) Output destination of deadlock and timeout information
(2) Actions to be taken by the HiRDB administrator
(3) Referencing deadlock and timeout information
(4) Using deadlock and timeout information
(5) Deleting unneeded deadlock/timeout information files

(1) Output destination of deadlock and timeout information

Deadlock information and timeout information are output to the following files, which are called the deadlock/timeout information files:

The file-name is determined by HiRDB as follows on the basis of the date and time the deadlock or timeout occurred:

[Figure]

(2) Actions to be taken by the HiRDB administrator

To output deadlock/timeout information, the following specifications must be made in the system common definition:

  1. Specify in the pd_lck_deadlock_info operand that deadlock information and timeout information are to be output.
  2. Specify a lock-release wait time value in the pd_lck_wait_timeout operand.

(3) Referencing deadlock and timeout information

When the following messages are output, the deadlock or timeout information should be referenced:

Deadlock or timeout information can be referenced with an OS command (for example, the cat command or the vi command). The KFPS00441-I and KFPS00451-I messages display the file name to be specified in these commands. For details about the cat and vi commands, see the OS documentation.

For details on the deadlock and timeout information that is output, see 8.6.2 Deadlock information that is output and 8.6.3 Timeout information that is output.

(4) Using deadlock and timeout information

It might be possible to reduce the frequency of deadlock and timeout occurrences by changing the UAP access sequence or widening the UAP lock range. It is important to use the deadlock and timeout information that is output to reevaluate the resources that cause the deadlock or timeout. For details on the actions to be taken with respect to the resources that result in deadlock or timeout, see the HiRDB Version 9 UAP Development Guide.

(5) Deleting unneeded deadlock/timeout information files

HiRDB does not delete deadlock/timeout information files. Such files must be deleted by the HiRDB administrator when the files are no longer needed. The following deletion procedures are provided.

(a) With a HiRDB command

The pdcspool command can be used to delete unneeded deadlock/timeout information files. However, the pdcspool command deletes all troubleshooting information files under $PDDIR/spool. To delete only deadlock/timeout information files, use the method described below in (c) With an OS command.

(b) With a HiRDB function

If all is specified in the pd_spool_cleanup_interval_level operand, HiRDB deletes deadlock/timeout information files periodically. The default is that HiRDB deletes them every 24 hours, but you can change this deletion interval with the pd_spool_cleanup_interval operand.

If all is also specified in the pd_spool_cleanup_level operand, HiRDB also deletes deadlock/timeout information files when it starts.

(c) With an OS command

Use an OS function (the OS's rm command, for example) to delete a deadlock/timeout information file. For details about the rm commands, see the OS documentation.