Performance Tuning Siebel Software on the Sun Platform

7.6 <strong>Tuning</strong> <strong>Siebel</strong> Standard Oracle Database and Sun Storage
The size of the database used was approximately 140 Gbytes. The database was built to
simulate customers with large transaction volumes and data distributions that
represented the most common customer data shapes. Table 7.6 shows a sampling of
record volumes and sizes in the database for key business entities of the standard <strong>Siebel</strong>
volume database.
Business Entity
Database Table
Name
Number of
Records
Size in Kbytes
Accounts S_ORG_EXT 1,897,161 3,145,728
Activities S_EVT_ACT 8,744,305 6,291,456
Addresses S_ADDR_ORG 3,058,666 2,097,152
Contacts S_CONTACTS 3,366,764 4,718,592
Employees S_EMPLOYEE_ATT 21,000 524
Opportunities S_OPTY 3,237,794 4,194,304
Orders S_ORDER 355,297 471,859
Products S_PROD_INT 226,000 367,001
Quote Items S_QUOTE_ITEM 1,984,099 2,621,440
Quotes S_QUOTE_ATT 253,614 524
Service Requests S_SRV_REQ 5,581,538 4,718,592
Table 7.6
7.6.1 Optimal Database Configuration
Creating a well-planned database to begin with will require less tuning/reorganizing
during runtime. While many resources are available to facilitate creation of highperformance
Oracle databases, most tuning engineers would find themselves tweaking a
database consisting of thousands of tables and indexes, piece by piece. This is both time
consuming and prone to mistakes. Eventually one would end up rebuilding the entire
database from scratch.
The following approach provides an alternative to tuning a pre-existing, pre-packaged
database:
1. Measure the exact space used by each object in the schema. The
dbms_space packages provide the accurate space used by an index or a table.
Other sources like dba_free_space only tell you “how much is free” from the
total allocated space, which is always more. Next, run the benchmark test and
again measure the space used. The difference will result in an accurate report of
“how much each table/index grows during the test.” One can use this data to rightsize
all of the tables, such as the capacity planned for growth during the test. Also
the data can be used to figure out and concentrate on only the hot tables used by
the test.
2. Create a new database with multiple index and data tablespaces. The idea is
to place all equi-extent-sized tables into their own tablespace. Keeping the data
and index objects in their own tablespace reduces contention and fragmentation,
<strong>Performance</strong> <strong>Tuning</strong> <strong>Siebel</strong> <strong>Software</strong> on the Sun Platform Page 39