Siebel Installation Guide for UNIX > Configuring the RDBMS > Configuring an IBM DB2 UDB Database for Siebel Applications >
Guidelines for Creating DB2 UDB Table Spaces
This topic is part of Configuring an IBM DB2 UDB Database for Siebel Applications. The Siebel Database installation process described in Configuring the Siebel Database specifies the table spaces in which to store your Siebel tables and indexes. A Siebel Database on DB2 UDB requires at least four table spaces using database-managed space (DMS). Each table space can have one or more table space containers to store the data. Create a minimum of four DB2 UDB table spaces to hold your tables and indexes: a 4-KB, a 16-KB, and a 32-KB table space, for your various sized tables, and an additional table space to hold your indexes. The table spaces must be created as database-managed space. Use a small, nonproduction environment for testing purposes. Observe the following guidelines when creating table spaces:
- Create at least four DB2 UDB table spaces for tables of various sizes, as shown in Table 11. Using the default table space names is recommended.
Table 11. DB2 UDB Table Space Values for Non-Unicode and Unicode-Enabled Databases
|
|
|
|
Non-Unicode Database |
SIEBEL_4K
|
IBMDEFAULTBP
|
2 GB |
Table space name for tables with row sizes less than 4006 bytes. |
SIEBEL_16K
|
BUF16K
|
300 MB |
Table space name for tables with row sizes from 4006 bytes through 16,293 bytes. |
SIEBEL_32K
|
BUF32K
|
100 MB |
Table space name for tables with row sizes greater than 16,293 bytes. |
Unicode-Enabled Database |
SIEBEL_4K
|
IBMDEFAULTBP
|
3 GB |
Table space name for tables with row sizes less than 4006 bytes. |
SIEBEL_16K
|
BUF16K
|
700 MB |
Table space name for tables with row sizes from 4006 bytes through 16,293 bytes. |
SIEBEL_32K
|
BUF32K
|
100 MB |
Table space name for tables with row sizes greater than 16,293 bytes. |
- Create additional table spaces as required for individual tables, such as
S_DOCK_TXN_LOG . If you expect to have large, heavily used tables, put these in their own table space.
- Create at least a 4-KB, 16-KB, and 32-KB temporary table space to use for sorting and other SQL processing as described in the following topics. If you do not create them, your database will experience serious performance and stability problems. Use system-managed space (SMS) for all temporary table spaces. Make sure these temporary table spaces are expandable to 2 GB for storage purposes.
- If you intend to use the DB2 Load utility to populate EIM tables, this method makes the table space in which the EIM table resides unavailable for the duration of the load. Placing the EIM tables in one or more separate table spaces allows concurrent activity on the database while the load utility is running.
- To override default storage parameters, such as the table space definitions, see Guidelines for Overriding DB2 UDB Default Table Spaces for Database Objects.
- Record the table space names in Deployment Planning Worksheet.
|