It is always a challenge when supporting large Siebel Enterprise applications when we have to troubleshoot a particular user issue. The very first question any DEV/Oracle person would ask is to provide them with the detailed logging from the user session for analysis.
I have posted an earlier article on the logging for specific user, but see that it does not work as expected in some scenarios. So listing this method which I follow personally when troubleshooting issues.
In this method, we are first looking for the server in which the user is connected to and increasing the logging on just that one server thereby limiting the overall impact of increasing the logging during business hours.
Steps:
1. Get the user login ID for which we need the logs
2. Login to Siebel server manager using the command:
srvrmgr /g <gatewayname> /e <enterprisename> /u <username> /p <password>
3. Get the active session of the user
srvrmgr> list session for login USER_NAME
SV_NAME CC_ALIAS CG_ALIAS TK_TASKID TK_PID TK_DISP_RUNSTATE TK_IDLE_STATE TK_PING_TIME TK_HUNG_STATE DB_SESSION_ID OM_LOGIN OM_BUSSVC OM_VIEW OM_APPLET OM_BUSCOMP
------- -------- -------- --------- ------ ---------------- ------------- ------------ ------------- ------------- -------- --------- ------- --------- ----------
SERVER1 SCCObjMgr_enu CallCenter 35653120 18688 Running FALSE Shared Connection Id: USER_NAME Completed : Workflow Process Manager (RunProcess) Completed: Business Servi
Note the task ID for the particular user session.
4. Increase the component logging by connecting to the server where user session is running
srvrmgr> set server SERVER1
srvrmgr:server1> change evtloglvl %=5 for comp SCCObjMgr_enu
5. Logon to SERVER1 and search by the task ID got from step 3 in the <siebelserver home>/log folder. This will be the user session log
6. Turn off the logging once done
srvrmgr:server1> change evtloglvl %=1 for comp SCCObjMgr_enu
This method will also increase the details in other user sessions that are connected to that Object Manager on the server, but if needed for short term analysis this can be an effective method. Any other alternative and efficient inputs from the community are greatly appreciated.
-Shyam
I have posted an earlier article on the logging for specific user, but see that it does not work as expected in some scenarios. So listing this method which I follow personally when troubleshooting issues.
In this method, we are first looking for the server in which the user is connected to and increasing the logging on just that one server thereby limiting the overall impact of increasing the logging during business hours.
Steps:
1. Get the user login ID for which we need the logs
2. Login to Siebel server manager using the command:
srvrmgr /g <gatewayname> /e <enterprisename> /u <username> /p <password>
3. Get the active session of the user
srvrmgr> list session for login USER_NAME
SV_NAME CC_ALIAS CG_ALIAS TK_TASKID TK_PID TK_DISP_RUNSTATE TK_IDLE_STATE TK_PING_TIME TK_HUNG_STATE DB_SESSION_ID OM_LOGIN OM_BUSSVC OM_VIEW OM_APPLET OM_BUSCOMP
------- -------- -------- --------- ------ ---------------- ------------- ------------ ------------- ------------- -------- --------- ------- --------- ----------
SERVER1 SCCObjMgr_enu CallCenter 35653120 18688 Running FALSE Shared Connection Id: USER_NAME Completed : Workflow Process Manager (RunProcess) Completed: Business Servi
Note the task ID for the particular user session.
4. Increase the component logging by connecting to the server where user session is running
srvrmgr> set server SERVER1
srvrmgr:server1> change evtloglvl %=5 for comp SCCObjMgr_enu
5. Logon to SERVER1 and search by the task ID got from step 3 in the <siebelserver home>/log folder. This will be the user session log
6. Turn off the logging once done
srvrmgr:server1> change evtloglvl %=1 for comp SCCObjMgr_enu
This method will also increase the details in other user sessions that are connected to that Object Manager on the server, but if needed for short term analysis this can be an effective method. Any other alternative and efficient inputs from the community are greatly appreciated.
-Shyam
it didn;t work\
ReplyDelete