Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 12.0.1 » SQL Anywhere Server - SQL Usage » Performance improvements, diagnostics, and monitoring » Application profiling tutorials » Tutorial: Diagnosing deadlocks

 

Lesson 3: Reviewing blocked connection data

The Application Profiling mode provides a graphical representation of the connections participating in the deadlock. It also provides a Connection Blocks tab that provides additional information about the blocked connections.

 Review blocked connection data
  1. Open the analysis file created during the tracing session as follows:

    1. In Sybase Central, click Application Profiling » Open Analysis File Or Connect To A Tracing Database.

    2. Click In A Tracing Database.

    3. Click Open.

    4. In the User ID field, type DBA.

    5. In the Password field, type sql.

    6. In the Action dropdown list, click Connect To A Running Database On This Computer.

    7. In the Database Name field, type app_profiling.

    8. Click Connect.

  2. View the graphical representation of the deadlock as follows:

    1. In the Application Profiling Details pane click the Status tab and choose the most recent ID from the Logging Session ID list.

      If the Application Profiling Details pane does not appear, click View » Application Profiling Details.

    2. At the bottom of the Application Profiling Details pane, click the Deadlocks tab. The most recent deadlock appears. Click the Deadlock list to view additional deadlocks.

    3. The following image shows how the UPDATE statements created a deadlock condition.

      For each connection, a table is shown with a arrow pointing at the other connection.

    Each connection involved in the deadlock is represented by a table with the following fields:

    • Connection Name   This field shows the user ID that opened the connection.

    • SQL Statement   This field shows the actual statement involved in the deadlock. In this case, the deadlock was caused by the UPDATE statements found in the procedures you executed from each instance of Interactive SQL.

    • Owning Connection ID   This field shows the ID of the connection that blocked the current connection.

    • Record ID   This field shows the ID of the row that the current connection is blocked on.

    • Rollback Operation Count   This field shows the number of operations that must be rolled back as a result of the deadlock. In this case, the procedures contained only the UPDATE statements, so the count is 0.

  3. To view additional deadlock information, such as how often they occur and how long they last, use the Connection Blocks tab, as follows:

    1. In the Application Profiling Details pane, click the Database Tracing Data tab.

    2. Click the Connection Blocks tab, just above the Database Tracing Data tab.

    3. The Connection Blocks tab appears, displaying the block time, unblock time, and duration of each blocked connection.

  4. You have completed the application profiling tutorial on deadlocks. Click Connections » Disconnect, and then close Sybase Central.

 See also