Bookshelf Home | Contents | Index | Search | PDF |
Siebel Server Installation Guide for Microsoft Windows > Creating the Oracle Database >
Planning the Distribution of Your Database Objects
Regardless of the RDBMS you implement, and your chosen disk arrangement, be certain that you properly distribute the following types of database objects:
- Database log or archive files
- Rollback segments
- Temporary work space used by the database
- Tables and indexes
In most implementations, the Siebel tables listed in Table 29 and their corresponding indexes tend to be either the most commonly used, or they have the potential to be large in some, or in all, deployments. For example, the tables
S_EVT_ACT, S_CONTACT
,and
S_ORG_EXT
are large in all sizeable deployments of Siebel eBusiness Applications.These tables and indexes should be separated across devices. As a general rule, indexes should be in a different tablespace and, if possible, on different physical devices from the tables on which they are created.
Planning Database Distribution if a RAID Disk Array Is Not Used
If a RAID device is not in use, even if space is at a premium, you must separate the indexes whose names end with
_P1
from the tables on which they are created. These tables are heavily used in join operations.If you will make frequent use of Siebel Enterprise Integration Manager (EIM), you may want to put the interface tables and indexes (names starting with
EIM_
) on different devices from the Siebel base tables. Both tables are accessed simultaneously during EIM operations.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Server Installation Guide for Microsoft Windows Published: 25 June 2003 |