Lock tree
Home > Select Project > Analysis > Lock Tree
This tool analyzes the trend of locks that occurred during the day. This function allows you to visually check the tree structure of the session that generated the lock (lock holder) and the session waiting for the lock (lock waiter). You can analyze the relationship between the holder and waiter of the lock that occurred at a specific time point.
Key features are as follows:
-
Lock trend analysis: The trends of locks that occurred during the set search period are traced over time and displayed in a graph. This allows you to visually check how the locks are created and resolved.
-
Check lock holder and waiter: You can see the holder and waiter for each lock in a tree structure. Through this, when a specific lock occurs, you can check the relationship between the session that generated the lock and the waiting session.
-
Inter-session relationship analysis: By analyzing the relationship between the session that generated the lock and the waiting session, you can identify the cause of the lock that occurred during the query execution and transaction handling.
This allows the database administrator to quickly identify and resolve lock-related issues and optimize the database performance.
Basic screen guide
Set the desired 
date and time, and then select an instance from the 
list. If a lock occurs at the set time, lock wait sessions and the retrieved data appear in the table at the bottom of the screen.
Column information guide
| Item | Description |
|---|---|
| tranindex | Transaction index |
| user | Database user name |
| host | Host name of CAS that performs transactions |
| pid | Broker process ID |
| program | Client program name |
| query_time | Total execution time of active queries (unit: second) |
| tran_time | Total execution time of transactions (unit: second) |
| transtatus | Transaction status |
| lock_holder | List of transactions that own a lock if transactions are waiting for the lock |
| sql_id | ID for SQL text |
| sql_text | Query statement being executed (up to 30 characters) |
| sql_param | Literal value separated from query |
| sql_hash | Hash value of query (internal WhaTap control value) |