Performance Tuning Siebel Software on the Sun Platform

More documents

Recommendations

Info

9 Scripts, Tips, and Tricks for Diagnosing <strong>Siebel</strong> on the Sun Platform We found the following tips to be very helpful for diagnosing performance and scalability issues while running <strong>Siebel</strong> on the Sun platform. 9.1 To Monitor <strong>Siebel</strong> Open Session Statistics You can use the following URLs to monitor the amount of time that a <strong>Siebel</strong> end user transaction is taking within your <strong>Siebel</strong> enterprise. This data is updated near realtime. Call Center eSales eService eChannel http://webserver:port/callcenter_enu/_stats.swe?verbose=high http://webserver:port/esales_enu/_stats.swe?verbose=high http://webserver:port/eservice_enu/_stats.swe?verbose=high http://webserver:port/prmportal_enu/_stats.swe?verbose=high Table 10.1 The stat page provides a lot of diagnostic information. Watch out for any rows that are in bold. They represent requests that have been waiting for over 10 seconds. 9.2 To List the Parameter Settings for a <strong>Siebel</strong> Server Use the following server command to list all parameter settings for <strong>Siebel</strong> server: srvrmgr> list params for server servername comp component show PA_ALIAS, PA_VALUE Parameters of interest are MaxMTServers, MinMTSServers, MaxTasks, MinSharedDbConns, MaxSharedDbConns, MinTrxDbConns. 9.3 To Find Out All OMs Currently Running for a Component Use the following server command to find out all OMs that are running in a <strong>Siebel</strong> enterprise, sorted by <strong>Siebel</strong> component type: $> srvrmgr /g gateway /e enterprise /u sadmin /p sadmin -c "list tasks for comp component show SV_NAME, CC_ALIAS, TK_PID, TK_DISP_RUNSTATE" | grep Running | sort -k 3 | uniq -c | sort -k 2,2 -k 1,1 The following output came from one of the runs: 47 siebelapp2_1 eChannelObjMgr_enu 19913 Running 132 siebelapp2_1 eChannelObjMgr_enu 19923 Running 133 siebelapp2_1 eChannelObjMgr_enu 19918 Running 158 siebelapp2_1 eChannelObjMgr_enu 19933 Running 159 siebelapp2_1 eChannelObjMgr_enu 19928 Running 118 siebelapp2_1 eSalesObjMgr_enu 19943 Running 132 siebelapp2_1 eSalesObjMgr_enu 19948 Running 156 siebelapp2_1 eSalesObjMgr_enu 19963 Running 160 siebelapp2_1 eSalesObjMgr_enu 19953 Running <strong>Performance</strong> <strong>Tuning</strong> <strong>Siebel</strong> <strong>Software</strong> on the Sun Platform Page 58
160 siebelapp2_1 eSalesObjMgr_enu 19958 Running 169 siebelapp2_1 eServiceObjMgr_enu 19873 Running 175 siebelapp2_1 eServiceObjMgr_enu 19868 Running 178 siebelapp2_1 eServiceObjMgr_enu 19883 Running 179 siebelapp2_1 eServiceObjMgr_enu 19878 Running 179 siebelapp2_1 eServiceObjMgr_enu 19888 Running 45 siebelapp2_1 SCCObjMgr_enu 19696 Running 45 siebelapp2_1 SCCObjMgr_enu 19702 Running 51 siebelapp2_1 SCCObjMgr_enu 19697 Running 104 siebelapp2_1 SCCObjMgr_enu 19727 Running Run States are Running, Online, Shutting Down, Shutdown, and Unavailable. Run Tasks should be evenly distributed across servers and close to MaxTasks. 9.4 To Find Out the Number of Active Servers for a Component Use the following server command to find out the number of active MTS Servers for a component: srvrmgr> list comp component for server servername show SV_NAME, CC_ALIAS, CP_ACTV_MTS_PROCS, CP_MAX_MTS_PROCS The number of active MTS servers should be close to the number of Max MTS servers. 9.5 To Find Out the Tasks for a Component Use the following server command to find the tasks for a component: srvrmgr> list task for comp component server servername order by TK_TASKID Ordering by task id places the most recently started task at the bottom. It is a good sign if the most recently started tasks (that is, those started in the past few seconds or minutes) are still running. Otherwise, further investigation is required. 9.6 To Set Detailed Trace Levels on the <strong>Siebel</strong> Server Components (<strong>Siebel</strong> OM) Log in to svrmgr and execute the following commands: Change evtloglvl taskcounters=4 for comp sccobjmgr change evtloglvl taskcounters=4 for comp eserviceobjmgr change evtloglvl taskevents=3 for comp sccobjmgr change evtloglvl taskevents=3 for comp eserviceobjmgr change evtloglvl mtwaring=2 for comp sccobjmgr change evtloglvl mtwaring=2 for comp eserviceobjmgr change evtloglvl set mtInfraTrace = True 9.7 To Find Out the Number of GUEST Logins for a Component Use the following server command to find out the number of GUEST login for a component: <strong>Performance</strong> <strong>Tuning</strong> <strong>Siebel</strong> <strong>Software</strong> on the Sun Platform Page 59
Page 1 and 2:
Performance <stron
Page 3 and 4:
Abstract This paper discusses the p
Page 5 and 6:
7.6.6 Oracle Parameters Tun
Page 7 and 8: 1 Tuning for Price
Page 9 and 10: 2 Siebel Applicati
Page 11 and 12: 3 Optimal Sun/Siebel</stron
Page 13 and 14: 3.1 Hardware and Software</
Page 15 and 16: 5 10,000 Concurrent Users: Test Res
Page 17 and 18: 6 Siebel Scalabili
Page 19 and 20: Cost per Siebel Us
Page 21 and 22: 7.1 Tuning Solaris
Page 23 and 24: 7.1.3 The Solaris Kernel and TCP/IP
Page 25 and 26: In the file $SIEBEL_ROOT/bin/enu/ua
Page 27 and 28: 7.2.3 Assignment Manager Tu
Page 29 and 30: MQ series parameter tuning: PERFQMG
Page 31 and 32: Investigating the Reason for the Fa
Page 33 and 34: let a Siebel proce
Page 35 and 36: Description The reason for this sym
Page 37 and 38: Parameter Scope Default Tuned Value
Page 39 and 40: 7.6 Tuning <strong
Page 41 and 42: 86 MB/second 57 MB/second Figure 7.
Page 43 and 44: DATA_51200K INDX_512K DATA_5120K TE
Page 45 and 46: 7.6.4 Solaris MPSS Tuning</
Page 47 and 48: Siebel Object Name
Page 49 and 50: instance_name=oramst job_queue_proc
Page 51 and 52: ORAPERF.S_PRI_LST T4 WHERE T4.PAYME
Page 53 and 54: the database during peak load. In t
Page 55 and 56: use connection pooling, so you woul
Page 57: Oracle Database Server 1. Larger th
Page 61 and 62: 9.10 To Produce a Stack Trace for t
Page 63 and 64: Count indv cuml rcnt nsec Lock Call
Page 65 and 66: 5. Once the user has stopped at the
Page 67 and 68: 10 Appendix A: Transaction Response
Page 69 and 70: eSls1_115DDSubCategory1.3 0.125 0.1
Page 71 and 72: CC3_2newSolution 0.047 0.136 3.281
Page 73 and 74: 11 Appendix B: Database Objects Gro
Page 75 and 76: S_OPTY_BU_M8 INDEX 2,334,720 S_ORDE
Page 77 and 78: log file parallel write 550,101 515
Page 79: Acknowledgements Thanks to
show all

Performance Tuning Siebel Software on the Sun Platform

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?