Troubleshooting Poor Performing SQL at the Database Level Using Workload Tagging

This topic is part of Analyzing Generated SQL for Performance Issues.

Siebel workload tagging is a diagnostic tool that tags SQL statements generated and executed by Siebel CRM running on Oracle Database. This tool helps database administrators trace and troubleshoot poor performing SQL or excessive workload at the database level.

Note: Siebel workload tagging is available only for Siebel applications running on Oracle Database.

When workload tagging is enabled, specified Siebel Application Object Manager-generated SQL statements (SELECT, INSERT, UPDATE, DELETE) are tagged with workload tagging attributes. The values for these attributes include the following:

CLIENT_IDENTIFIER: component_name,servername,taskID,userID,FlowID:SarmID
ACTION: View Name
MODULE: Business Component Name

Note: The length of the previous attribute values is limited to 64 bytes for CLIENT_IDENTIFIER, 32 bytes for ACTION, and 48 bytes for MODULE. Truncation occurs when the length exceeds these limitations.

When poor performing SQL statements are suspected, the database administrator can use this tagging information to trace details about the generated SQL and the user that initiated it. Database administrators can then use Oracle Enterprise Manager to find the component task and log detail for more in-depth analysis of the performance issue. Alternatively, you can use SQL*Plus or similar tools to query the Oracle Database V$SESSION view to look up the CLIENT_IDENTIFIER, ACTION, and MODULE attributes by using SQL_ID of the SQL statement.

This topic contains the following information: