Siebel Server Installation Guide for UNIX > Creating the DB2 Universal Database for Windows and UNIX > Creating the Database >

Creating Tablespaces


The Siebel Database Server installation process specifies the tablespaces in which to store your Siebel tables and indexes.

A Siebel DB2 database consists of at least four tablespaces using database-managed space (DMS). Each tablespace can have one or more tablespace containers to store the data.

It is recommended that you use a small, non-production environment for testing purposes. You should create a minimum of four DB2 tablespaces to hold your tables and indexes—a 4 KB, a 16 KB, and a 32 KB tablespace, for your various sized tables, and a tablespace to hold your indexes. The tablespaces must be created as database-managed space.

To create the tablespaces

  1. Create at least four DB2 tablespaces for tables of various sizes as shown in Table 24.

Table 24.  DB2 Tablespace Values for Both Non-Unicode and Unicode-Enabled Databases
DB2 Tablespace Name
Bufferpool Name
Recommended Value
Description
Non-Unicode-Enabled Database
SIEBEL_4K
IBMDEFAULTBP
2 GB
Tablespace name for tables with row sizes of at most 4005 bytes.
SIEBEL_16K
BUF16K
300 MB
Tablespace name for tables with row sizes from 4006 bytes through 16,293 bytes.
SIEBEL_32K
BUF32K
100 MB
Tablespace name for tables with row sizes greater than 16,293 bytes.
Unicode-Enabled Database
SIEBEL_4K
IBMDEFAULTBP
3 GB
Tablespace name for tables with row sizes of at most 4005 bytes.
SIEBEL_16K
BUF16K
700 MB
Tablespace name for tables with row sizes from 4006 bytes through 16,293 bytes.
SIEBEL_32K
BUF32K
100 MB
Tablespace name for tables with row sizes greater than 16,293 bytes.

NOTE:  It is recommended that you use the default tablespace names.

  1. Create any additional tablespaces that may be used for storing individual tables, such as S_DOCK_TXN_LOG. If you expect to have large, heavily used tables, put these in their own tablespace.
  2. Create at least a 4 KB, 16 KB, and 32 KB temporary tablespace to use for sorting and other SQL processing as described in the following sections. If you do not create them, your database will experience serious performance and stability problems. It is recommended that you use system-managed space (SMS) for all temporary tablespaces. These temporary tablespaces should also be expandable to 2 GB for storage purposes.
  3. NOTE:  Good practice dictates that you have many tablespaces that contain tables and indexes so that not all indexes reside in one tablespace. Otherwise, you may run out of pages.

  4. Create at least one container per tablespace.
  5. Record the tablespace names on the Deployment Planning Worksheets.
  6. NOTE:  If you intend to use the DB2 Load utility to populate EIM tables, be aware that it makes the tablespace in which the EIM table resides unavailable for the duration of the load. Placing the EIM tables in one or more separate tablespaces allows concurrent activity on the database while the load utility is running.


 Siebel Server Installation Guide for UNIX 
 Published: 24 June 2003