|
Siebel Installation Guide for Microsoft Windows > Configuring the RDBMS > Configuring an IBM DB2 Database for Siebel Business Applications >
Guidelines for Creating IBM DB2 Tablespaces
The Siebel database installation process described in Installing the Siebel Database on the RDBMS specifies the tablespaces in which to store your Siebel tables and indexes. A Siebel database on IBM DB2 requires at least four tablespaces using database-managed space (DMS). Each tablespace can have one or more tablespace containers to store the data. 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 an additional tablespace to hold your indexes. The tablespaces must be created as database-managed space. Use a small, nonproduction environment for testing purposes. This topic is part of Configuring an IBM DB2 Database for Siebel Business Applications. Observe the following guidelines when creating tablespaces:
- Create at least three IBM DB2 tablespaces for tables of various sizes, as shown in Table 26. Using the default tablespace names is recommended.
Table 26. IBM DB2 Tablespace Values for Non-Unicode and Unicode-Enabled Databases
|
|
|
|
Non-Unicode Database |
SIEBEL_4K |
BUF4K |
2 GB |
Tablespace name for tables with row sizes less than 4006 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 |
BUF4K |
4 GB |
Tablespace name for tables with row sizes less than 4006 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. |
- Create additional tablespaces as required for individual tables, such as S_DOCK_TXN_LOG. If you expect to have large, heavily used tables, then put these in their own tablespace.
- In addition, for performance reasons it is highly recommended that you create a separate tablespace for indexes. For example, you might create a tablespace named SIEBEL_IDX and using buffer pool BUF16K, with a page size of 16 KB, and with 3 GB allocated for this tablespace.
- Create at least 4-KB, 16-KB, and 32-KB temporary tablespaces to use for sorting and other SQL processing as described in the following topics. If you do not create them, then your database will experience serious performance and stability problems. Use system-managed space (SMS) for all of the temporary tablespaces. Make sure that these temporary tablespaces are expandable to 2 GB for storage purposes.
- If you intend to use the DB2 Load utility to populate EIM tables, then this method makes the tablespace in which EIM tables 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.
- To override default storage parameters, such as the tablespace definitions, see Guidelines for Overriding IBM DB2 Default Tablespaces for Database Objects.
- Record the tablespace names in Siebel Deployment Planning Worksheet.
|
