Siebel System Monitoring and Diagnostics Guide > Monitoring Siebel Server Run-Time Operations >

About Setting Log Levels for SQL Tagging

The Object Manager SQL Log (alias ObjMgrSqlLog) server component event type has an SqlTag event subtype. The SqlTag subtype sets the log level for an SQL tag at a lower lever than where SQL statements are typically logged. It enables logging of the SQL tags in the log file without logging the complete SQL statements.

The OM SQL Logging (ObjMgrSqlLog) and OM SQL Tagging (ObjMgrSqlTag) events are independent of each other and can coexist. The ObjMgrSqlLog event controls the level of SQL logging detail in an object manager log file. The ObjMgrSqlTag event controls whether SQL statements are tagged or not and how much tagging information is generated, irrespective of whether or not the SQL statements are logged in the log file. For example, if the ObjMgrSqlLog event log level is set to 1, neither the SQL statements nor the SQL tags are logged in the log files, even if the ObjMgrSqlTag subevent is active. Whereas, if the ObjMgrSqlLog event log level is set to 4, full details about the SQL information is generated in the log files. However, if the ObjMgrSqlTag subevent is not active, the SQL is not tagged, nor are the SQL tags logged in the log files.

If SQL tagging is active and the SQL Logging event is set at the SqlTag level, only the SQL tags are logged in the log files as shown in the following example:

Begin: Execute SqlObj 'Account' at 11160f10 with SqlTag=SCCObjMgr_enu,sdchs20i046,10485776,,SADMIN,00000089489108a8:50557,
Account,Account,Account List V

This configuration is useful in diagnosing long-running SQLs without generating too much SQL logging in the log files.

NOTE:  The END statement is logged so that you can run a script to identify log files where the BEGIN SQL tag statement is present, but there is no END statement. This syntax helps determine which log files might contain long-running SQL statements.

For information about setting log levels for SQL tagging, see Setting Log Levels for SQL Tagging.