Page History
...
Table 4-1 Database Overview view
| View |
|---|
...
| area | Description |
|---|---|
| Application | Displays the following application-related information: |
...
|
...
|
...
|
| In |
...
| DB2 | Displays the resource consumption breakdown of the database during the last minute or, in the Application context, from the beginning of the time slice. In addition to the resource distribution, the view displays the number of applications in each state during the last sample. The following information is displayed: |
...
|
...
|
...
|
...
|
...
|
About viewing Database locks
Displays lock wait duration for the selected Database during the last minute. The applications that are currently involved in a locking or blocking situation are displayed in tree format.Note:
| Info |
|---|
Since the Lock tree represents the locks that are currently occurring, and the lock breakdown represents the duration of locks occurring during the last minute, it is possible that a situation may occur whereby a lock was freed, but since the last minute has not yet passed, the lock tree will display the message ‘No locks detected' while the Lock Breakdown grid still shows lock duration. |
The following table provides a detailed explanation of the Lock Tree
Table 4-2 Database Locks view
| View |
|---|
...
| area | Description |
|---|---|
| Lock |
...
| tree | It is important to determine the following information for each blocking chain: |
...
|
...
The Lock Tree provides the necessary information to get to the root of the problem by providing information on applications currently involved in the blocking situation. A yellow lock indicates that the application is currently locking other applications but is not itself blocked. A red lock indicates the application is currently blocked by another application. Note that |
...
an application application may also block other applications while being blocked by itself. To gain a better understanding of the lock tree take a closer look at its structure. Notice that the application located in the root of each chain is the application that blocks all others. Each application directly blocks all applications positioned one level beneath it. The Lock Tree displays the application handle, program name, the object being blocked and the lock type. |
| Anchor | ||||
|---|---|---|---|---|
|
Displays information on a single connection with Microsoft SQL Server. Precise for SQL Server identifies an application by the following attributes:
- Application ID—a ID. A unique integer assigned to each user connection when the connection is made.
- Application identifiers such as program or database user.
When one of these attributes changes, a new application is recorded and displayed. The following table describes the information displayed in the Application overview.
Table 4-3 Application Overview
| View |
|---|
...
| area | Description |
|---|---|
| Application |
...
| tab | Displays the following information: |
...
|
...
|
...
|
...
|
...
|
...
|
| In DB2 tab (last minute) |
...
Displays the resource consumption breakdown of the application during the last minute (that is, 60 samples of the Collector). In addition to the resource distribution, the view displays the number of applications in each state during the last sample. It is important to remember that since this view only displays the last minute's activities, you will always be viewing the activities that occurred during the last minute and not the activities that occurred since the last refresh action. The following information is displayed: |
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
| Connection |
...
| tab | A connection includes application identifiers such as User, Login, and Machine. The following information is displayed: |
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
The following table describes the information displayed in the Application Text view.
Table 4-4 Application Text view
| View |
|---|
...
| area | Description |
|---|---|
| Text | Displays the text of the current statement. If the application is not active and executing a statement, a message notifying you that the application is not active and that no text is available is displayed. |
| Anchor | ||||
|---|---|---|---|---|
|
...
Table 4-5 Applications Holding Locks overview
| View |
|---|
...
| area | Description |
|---|---|
| Application |
...
| tab | Displays the following information: |
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
| In DB2 tab (last minute) |
...
Displays the resource consumption breakdown of the application during the last minute (that is, 60 samples of the Collector). In addition to the resource distribution, the view displays the number of applications in each state during the last sample. It is important to remember that since this view only displays the last minute's activities, you will always be viewing the activities that occurred during the last minute and not the activities that occurred since the last refresh action. The following information is displayed: |
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
| Connection |
...
| tab | A connection includes application identifiers such as User, Login, and Machine. The following information is displayed: |
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
About viewing information on the lock breakdown of an application that is holding locks
...
Table 4-6 Locks view for the Application Holding Locks entity
| View |
|---|
...
| area | Description |
|---|---|
| Lock |
...
| Tree | The Lock tree provides the necessary information to determine the following information for each blocking chain: |
...
|
...
|
...
|
About viewing the text of an application that is holding locks
...
Table 4-7 Statement Overview view
| View |
|---|
...
| area | Description |
|---|---|
| General |
...
| tab |
|
...
|
...
|
| In DB2 (Last minute) |
...
The following information is displayed: |
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
About viewing current Statement text
...
You can identify a performance problem by doing one or more of the following:
- Examining resource consumption of an entire database partition
- Observing the activity of a single application
- Examining a single connection
- Analyzing currently held lockslocks
| Anchor | ||||
|---|---|---|---|---|
|
The Current tag provides an almost real-time picture of the performance and behavior of your DB2 database partition. The Current tag displays information on the last time slice of activity, unless otherwise configured as for the last minute. Usually you will examine the activities of the entire database partition level to determine what is happening in your system. By examining the current activity at a database partition level of display, you can see how it is currently behaving and determine if there is an overall problem that affects all applications or if there is a problem with specific applications.
To examine resource consumption of an entire instance and database1 In
- In the database partition list, choose the database partition you want to analyze.
Do the following:
...
- On the View controls in the Main area, click Overview. This will show you a breakdown of resource consumption for the last minute.
| Anchor | ||||
|---|---|---|---|---|
|
The Association area of the Current tag lets you view which applications are currently connected to the database partition. You can observe the current state of the application and determine if it is active or waiting for a resource. You can also identify the application by different identifiers such as its login information, the machine it is running on, or the programs it is running. The currently active TSQL code is displayed for active applications.
To observe current application activity1 In
- In the database partition list, choose the database partition you want to analyze.
...
- On the Association controls in the Association area, select one of the following to focus your investigation on the applications that were active in SQL Server during the last minute:
- Active Applications
...
- Applications
...
| Anchor | ||||
|---|---|---|---|---|
|
You may need to explore a single running application, to obtain more information on it. In the Association area you can drill down to the specific application in question, and continue your analysis.
To examine a single connection1 In
- In the database partition list, choose the database partition you want to analyze.
...
- In the Association area, drill down to the application whose connection you want to analyze.
...
- Continue your analysis by examining its resource breakdown and its recent statements, during the last few minutes.
| Anchor | ||||
|---|---|---|---|---|
|
To be able to avoid a blocking situation, it is important to have an accurate picture of all the locks held in the system. This will help you understand if the lock system is tuned and if it is possible to avoid a potential blocking situation. Using Precise for DB2, you can now observe the locks currently held in the database partition and group them according to lock level and lock mode.
Locks can be viewed in two levels:
- Application context - . To see which application is locking you.
- DB partition context - . To see the Lock tree with details of all locks holding the application. To analyze locks currently held
...
- In the database partition list, choose the item you want to analyze.
...
- On the View controls in the Main area, click Locks and examine the locking contentions. Move the cursor over the locked application in the tree to display the text of the locked application.
Precise. Performance intelligence from click to storage. Learn more > >
...