Performance Tuning Siebel Software on the Sun Platform

More documents

Recommendations

Info

382 0 0 0 0 0 0 0 0 0 0 [heap]: 0x485c2c0 102100 0 0 0 0 0 0 0 0 0 0 libsscfdm: g_CTsharedLock 9.13 To “Truss” an OM 1. Modify siebmtshw: #!/bin/ksh . $MWHOME/setmwruntime MWUSER_DIRECTORY=${MWHOME}/system LD_LIBRARY_PATH=/usr/lib/lwp:${LD_LIBRARY_PATH} #exec siebmtshmw $@ truss -l -o /tmp/$$.siebmtshmw.trc siebmtshmw $@ 2. After you start up the server, this wrapper creates the truss output in a file named pid.siebmtshmw.trc in /tmp. 9.14 How to Trace the SQL Statements for a Particular <strong>Siebel</strong> Transaction If response times are high, or if you think that the database is a bottleneck, you can check how long the SQL queries are taking to execute by running a SQL trace on a LoadRunner script. The SQL trace is run through <strong>Siebel</strong> and tracks all of the database activity and how long things take to execute. If execution times are too high, there is a problem with the database configuration, which most likely is contributing to high response times. To run a SQL Trace on a particular script, follow these instructions: 1. Configure the <strong>Siebel</strong> environment to the default settings (that is, the component should have only one OM, and so on). 2. Open the LoadRunner script in question in the Virtual User Generator. 3. Place a breakpoint at the end of Action 1 and before Action 2. This will stop the user at the breakpoint. 4. Run a user. <strong>Performance</strong> <strong>Tuning</strong> <strong>Siebel</strong> <strong>Software</strong> on the Sun Platform Page 64
5. Once the user has stopped at the breakpoint, enable SQL tracing via srvrmgr: change evtloglvl ObjMgrSqlLog=4 for comp 6. Press Play, which will resume the user. 7. Wait until the user has finished. 8. Under the $SIEBEL_SERVER_HOME/enterprises// directory, there will be a log for the component that is running. This log contains detailed information on the database activity, including how long the SQL queries took to execute. Search for high execution times (greater than 0.01 seconds). 9. Once you are done, disable SQL tracing via srvrmgr: change evtloglvl ObjMgrSqlLog=0 for comp 9.15 Changing Database Connect Stringvi $ODBCINI and Editing the field .ServerName. 1. srvrmgr /g siebgateway /e siebel /u sadmin /p sadmin /s 2. At srvrmgr prompt: Verify and change the value of DSConnectString parameter: i. List params for named subsystems serverdatasrc ii. Change param DSConnectString= for named subsystems serverdatasrc. 9.16 Enabling/Disabling <strong>Siebel</strong> Components Disabling a Component 1. Bring up srvrmgr console: srvrmgr /g siebgateway /e siebel /u sadmin /p sadmin /s 2. Disable the component: disable comp 3. List the components and verify their status: list components Enabling a Component Disabling a component may disable the component definition. We may need to enable the component definition 1. Bring up srvrmgr console at enterprise level (just do not use "/s" switch). 2. srvrmgr /g siebgateway /e siebel /u sadmin /p sadmin 3. Enable the component definition: enable compdef (Note: This enables the component definition at all active servers; you may need to disable the component at servers where you don't need the component.) <strong>Performance</strong> <strong>Tuning</strong> <strong>Siebel</strong> <strong>Software</strong> on the Sun Platform Page 65
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 and 58: Oracle Database Server 1. Larger th
Page 59 and 60: 160 siebelapp2_1 eSalesObjMgr_enu 1
Page 61 and 62: 9.10 To Produce a Stack Trace for t
Page 63: Count indv cuml rcnt nsec Lock Call
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?