Using Workload Tagging to Troubleshoot Poor Performing SQL at the Database Level
Use the following procedure to diagnose and troubleshoot poor performing SQL at the database level using Oracle Enterprise Manager. For more information about Oracle Enterprise Manager, see the documentation on Oracle Technology Network.
To use workload tagging to troubleshoot poor performing SQL at the database level
Make sure that workload tagging is enabled.
Log in to Oracle Enterprise Manager.
Navigate to the Database Control Top Activity page.
From the Top Sessions section, select the Top Sessions view, and then drill down on the Session ID that you want to troubleshoot.
Click the General tab.
In the Client section, note the values in the Current Client ID field.
The format for this field is:
component_name,servername,taskID,userID,FlowID:SarmID
where:
component_name is the server component alias, for example SCCObjMgr_enu.
servername is the name of the Siebel Server from which the SQL originated.
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 task.
SarmID is the SARM ID of the task.
For example:
SCCObjMgr_enu,server1,10485770,SADMIN,000008814d7f1fe8:163