Hitachi

Hitachi Advanced Database Setup and Operation Guide


10.8.3 Checking whether the process of reserving locked resources has gone into wait status

This subsection described how to check whether the process of reserving locked resources has gone into wait status after execution of an application or command.

To check the transaction processing status:

  1. Execute the adbls -d cnct command.

    Check the connection ID of the target application or command. Check the item CID.

  2. Execute the adbls -d lock command.

    Compare the connection ID checked in step 1 with the connection ID displayed under CID. Then, check the item STATUS. If WAITING is displayed, the process of reserving the locked resources to be used by the target application or command has gone into wait status.

    If you cannot wait for other applications or commands that are using the locked resources to terminate, proceed to step 3.

  3. Execute the adbcancel command.

    Execute the adbcancel command to forcibly terminate other applications and commands that are using the locked resources.

To prevent the process of reserving locked resources from going into wait status when you execute an application or command, take whatever action is necessary based on the explanation in 6.23.3 Points to consider about locking during concurrent command execution

For details about the adbls -d cnct, adbls -d lock, and adbcancel commands, see the manual HADB Command Reference.

Note

If the type of locked resource is a table or pre-processing table, you can determine the table's ID by checking the RESOURCEID item that is output by the adbls -d lock command. You can then use the table ID as a search key to identify the table name of the table whose acquisition is being requested by application programs and commands. The following bullet points explain how to determine a table name from its table ID: