Last updated on MARCH 02, 2017
Applies to:Siebel CRM - Version 184.108.40.206  and later
Information in this document applies to any platform.
How to enable Workload Tagging and make it works in Siebel 8.1.1.x ?
As per Bookshelf, Siebel Performance Tuning Guide ( Version 8.1, Rev. A December 2012 ). Siebel Workload Tagging can be enabled by following below steps ( in page 169-170 )
1 Navigate to the Administration - Server Configuration screen, then the Components view.
2 Select the appropriate Siebel Application Object Manager for which you want to enable workload
tagging. For example, if the application you are using is Siebel Call Center for English, then select
Call Center Object Manager (ENU).
3 Click the Events subview, and then select the OCI SQL Tagging event type.
4 Set the Log Level as 4
After workload tagging is enabled, database administrators can use Oracle Enterprise Manager to
diagnose and troubleshoot the problematic generated SQL.
Our expectation is to capture CLIENT_IDENTIFIER, ACTION in v$session table. But till now we didnt find any records with CLIENT_IDENTIFIER, ACTION for siebel sessions.
Please clarify whether these steps are correct or not or is there any product bug in Siebel 8.1 ?
After performing the above steps, CLIENT_IDENTIFIER, ACTION in v$session table are still empty. Similarly in Oracle Enterprise Manager > Database Control Top Activity page> Top Sessions view> Client Section> Crrent Client ID is also empty.
Siebel Workload tagging does not seem to work.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms