1. Performance Tuning Guide
  2. About Specifying SQL Logging and SQL Tagging for Siebel Application Object Manager Components

About Specifying SQL Logging and SQL Tagging for Siebel Application Object Manager Components

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

SQL logging and SQL tagging are diagnostic tools that log and tag SQL statements generated and executed by Siebel CRM. When used in conjunction with SQL logging, SQL tagging can help administrators trace long-running or slow-performing SQL queries back to the user or action that triggered them. You can also use these tools to review generated SQL in a development or test environment after making configuration changes in Siebel Tools.

Note: SQL tagging must be used in development or test environments only. It is strongly recommended not to use this diagnostic feature in the production environment, because it generates a large number of log entries, which could impact performance negatively and lead to running out of disk space on the Siebel Server.

  • SQL logging controls the level of SQL logging detail in a log file for an object manager-based component. To set SQL logging for a component, set the Object Manager SQL Log (alias ObjMgrSqlLog) event to an appropriate value. For example, specify the event value for a Siebel Application Object Manager component such as Call Center Object Manager (ENU).

  • SQL tagging controls whether or not SELECT statements are tagged for an object manager-based component. SQL tagging also controls whether or not to log additional information, such as the name of a business component. SQL tagging is primarily used during the development phase. To set SQL tagging for a component, set the OM SQL Tagging (alias ObjMgrSqlTag) event to an appropriate value. By default, SQL tagging is disabled.

Caution: SQL tagging changes the format and content of the SQL SELECT statement by adding a bind, which inhibits the use of Oracle stored outlines, if they exist.

With SQL tagging, data that can be logged includes the server component name, server name, task ID, user ID, flow ID (with Siebel ARM ID), business object name, business component name, and view name. Which elements are logged depends on the level set for the event.

For instructions on how to use SQL tagging and logging to log and tag generated SQL statements at the server component level, see Siebel System Monitoring and Diagnostics Guide.