Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
When you have a specific application or request that is problematic, you can perform a request trace analysis to determine the problem. Request trace analysis configures the Database Tracing Wizard to narrow diagnostic data gathering to only the user, connection, or request that is experiencing the problem.
To start a tracing session, TCP/IP must be running on the database server(s) on which the tracing database and production database are running.
You must have the DIAGNOSTICS system role, and the MANAGE PROFILING, SERVER OPERATOR, and SELECT ANY TABLE system privileges.
Context and remarks
Using the various data viewing tools in Application Profiling mode, you can identify any potential conflicts or bottlenecks.
In Sybase Central, use the SQL Anywhere 16 plug-in to connect to the database.
Click Mode » Application Profiling.
If the Application Profiling Wizard appears, click Cancel.
Right-click the database and click Tracing or click Tracing » Configure And Start Tracing.
Follow the instructions in the Database Tracing Wizard.
When you are done gathering tracing data, right-click the database and click Tracing » Stop Tracing With Save.
In the Application Profiling Details pane, click Open An Analysis File Or Connect To A Tracing Database.
Click In A Tracing Database, and click Open.
Complete the User Name and Password fields and click OK.
In the Application Profiling Details pane, click the last entry in the Logging Session ID list.
Click Database Tracing Data tab at the bottom of the Application Profiling Details pane.
Discuss this page in DocCommentXchange.
|Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0|