SQL Tagging to trace queries in Siebel

Starting with Siebel Fix Pack 8.1.1.1 and later, SQL tagging feature provides the ability to trace the origin of long-running or slow-performing SQL statements. After SQL tagging is enabled (from Siebel), tagging information is added to the Siebel Application Object Manager. This feature is only available for SELECT. Other statements such as INSERT, UPDATE, DELETE or MERGE are not tagged.

 

SQL Tagging Format

SQL tagging information is formatted as a comma-separated list of values using the following syntax:
<componentname>,<servername>,<taskid>,<userid>,<flowid:sarmid>,<busobjname>,<buscompname>,<viewname>

 

where:

  • componentname is the alias of the component.
  • servername is the name of the Siebel Server on which the component or task is running.
  • taskid is the task ID of the user who generated the query.
  • userid is the login name of the user who generated the query.
  • flowid is the flow ID of the component or task.
  • sarmid is the SARM ID of the component or task.
  • busobjname is the business object name.
  • buscompname is the business component name.
  • viewname is the view name.

 

The tagged sql is returned as bind variable inside the <select list>, in the nth position, before the FROM clause. It will the bind variable label as :1, the rest of the statement will as usual. FROM clause, WHERE clause and ORDER (if exist). Note that the SQLID in Oracle SQL Tagging sentence will be different from a sentence without SQL Tagging.

 

sql_tagging_format

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s