|Bookshelf Home | Contents | Index | PDF|
The SQL tagging feature in Siebel Business Applications provides administrators with the ability to trace the origin of long-running or slow-performing SQL statements (queries) back to a specific task and user who triggered it. This topic describes the SQL tagging feature and syntax. It also provides sample code.
After SQL tagging is enabled, tagging information is added to the Siebel Application Object Manager (AOM)-generated SELECT statements. When a poor performing SQL statement is suspected, the database administrator can use this tagging information at the database level to trace which component task and user initiated the SQL without the need to reboot any Siebel Server or components. Database administrators can then find the component task log file for more in-depth analysis of the performance issue. For information about enabling SQL tagging, see Enabling and Disabling SQL Tagging.
NOTE: Other SQL statements generated by Siebel Application Object Manager, such as INSERT, UPDATE, and DELETE are not tagged. The SQL tagging feature is available for Siebel CRM version 220.127.116.11 and later, and Siebel CRM version 8.2.
The following is a sample of how a tagged SQL statement might appear in a log file when the SQL statement was generated from a Siebel Call Center (SCCObjMgr_enu AOM) component and an Oracle database. The changes made by the SQL tagging feature appear in italics.
|Siebel System Monitoring and Diagnostics Guide||Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.|