Siebel Installation Guide for UNIX > Configuring the RDBMS > Configuring an Oracle Database for Siebel Business Applications >
Guidelines for Creating Oracle Tablespaces
This topic is part of Configuring an Oracle Database for Siebel Business Applications.
Initial (minimum) tablespace allocation recommendations are as follows:
- Data: 5 GB
- Index: 5 GB
- Temp: 2 GB
- System: 2 GB
- Sysaux: 1 GB
This allocation is enough for a fresh installation of Oracle Database (Unicode-enabled or non-Unicode-enabled).
The following additional guidelines will help you in creating tablespaces:
- To improve performance on your production system, create at least two tablespaces for a Siebel implementation: one for indexes and one for data.
- Distribute objects that you anticipate to be large or points of contention by creating additional separate tablespaces (preferably on separate disk devices).
- Be sure that you, or whoever is responsible for setting up permissions, grant the Siebel table owner account the privilege and sufficient quota to create tables and indexes in these tablespaces.
Besides the table owner, the database user ID used for Siebel Marketing also requires additional rights at the database level within the OLTP schema. You must grant DROP TABLE, DROP INDEX, CREATE TABLE, and CREATE INDEX rights to this user. For more information, see Siebel Marketing Installation and Administration Guide.
- Set storage parameters for your data and index tablespaces. The Siebel database installation procedure does not set storage parameters for the objects it creates. The storage configuration for each object follows the default storage parameters of its tablespace. It is recommended that you create locally managed tablespaces by using the following syntax:
extent management local autoallocate segment space management auto;
- In a development or test environment, multiple Siebel Business Applications installations can coexist on one Oracle Database instance. Install each Siebel database under a separate table owner, so that each schema owner is unique.
- Function-based indexes based on expressions that require QUERY_REWRITE_ENABLED to equal TRUE are not supported. However, DESC (descending) indexes are supported, as in a standard schema.