Performance Tuning Siebel Software on the Sun Platform

semsys:seminfo_semmnu /etc/system 4096
semsys:seminfo_semopm /etc/system 4096
semsys:seminfo_semume /etc/system 2048
semsys:seminfo_semvmx /etc/system 32767
semsys:seminfo_semaem /etc/system 16384
msgsys:msginfo_msgmni /etc/system 4096
msgsys:msginfo_msgtql /etc/system 4096
msgsys:msginfo_msgmax /etc/system 16384
msgsys:msginfo_msgmnb /etc/system 16384
rlim_fd_max /etc/system 1024 16384
rlim_fd_cur /etc/system 64 16384
Table 7.6.7
7.6.8 SQL Query <strong>Tuning</strong>
During the course of the test, the most resource-intensive and long-running queries were
tracked. In general, the best way to tune a query is to change the SQL statement
(keeping the result set the same). The other method is to add or drop indexes so the
execution plan changes. The latter method is the only option in most benchmark tests.
We added four additional indexes to the <strong>Siebel</strong> schema which helped performance. With
<strong>Siebel</strong> 7.5 there is no support for CBO (cost-based optimization) with Oracle database.
CBO support is available in <strong>Siebel</strong> 7.7.
The following example shows one of the resource-consuming queries.
Buffer Gets Executions Gets per Exec % Total Hash Value
--------------- ------------ -------------- ------- ------------
220,402,077 35,696 6,174.4 33.2 2792074251
This query was responsible for 33% of the total buffer gets from all queries during the
benchmark tests.
SELECT
T4.LAST_UPD_BY,
T4.ROW_ID,
T4.CONFLICT_ID,
T4.CREATED_BY,
T4.CREATED,
T4.LAST_UPD,
T4.MODIFICATION_NUM,
T1.PRI_LST_SUBTYPE_CD,
T4.SHIP_METH_CD,
T1.PRI_LST_NAME,
T4.SUBTYPE_CD,
T4.FRGHT_CD,
T4.NAME,
T4.BU_ID,
T3.ROW_ID,
T2.NAME,
T1.ROW_ID,
T4.CURCY_CD,
T1.BU_ID,
T4.DESC_TEXT,
T4.PAYMENT_TERM_ID
FROM
ORAPERF.S_PRI_LST_BU T1,
ORAPERF.S_PAYMENT_TERM T2,
ORAPERF.S_PARTY T3,
<strong>Performance</strong> <strong>Tuning</strong> <strong>Siebel</strong> <strong>Software</strong> on the Sun Platform Page 50