Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS > Understanding Siebel Partitioning >
About Configuring Siebel Templates for Partitioning
Four of the storage control templates shipped with your Siebel eBusiness Applications are used for partitioning tables. The templates provide a set of 17 partitioned tables for the Horizontal product line, a set of 24 partitioned tables for Financial Services, and 18 partitioned tables for Siebel Industry Applications.
You can identify the templates for partitioning by the characters
_p_
in the middle of the .ctl file name. (If the characters_e_
appear at the end of the file name, then the template is for the EBCDIC code page encoding scheme.) All partitioning templates contain the same Siebel-recommended partitioning schema; the difference between the files is how nonpartitioned tables are stored.
- storage_p_1to1.ctl. Contains a partitioning scheme for a set of Siebel tables that use the ASCII encoding scheme. It also contains other nonpartitioned Siebel tables defined as one table per table space.
- storage_p_1to1_e.ctl. Contains a partitioning scheme for a set of Siebel tables that use the EBCDIC encoding scheme. It also contains other nonpartitioned Siebel tables defined as one table per table space.
- storage_p_group.ctl. Contains a partitioning scheme for a set of Siebel tables that use the ASCII encoding scheme. Most of the nonpartitioned tables are defined as multiple tables per table space.
- storage_p_group_e.ctl. Contains a partitioning scheme for a set of Siebel tables that use the EBCDIC encoding scheme. Most of the nonpartitioned tables are defined as multiple tables per table space.
NOTE: Table spaces that contain groups of tables are segmented.
The Siebel partitioning scheme uses two approaches. The first approach is to partition a table based on existing columns in the Siebel schema; for example, S_OPTY is partitioned by columns in the U1 index.
The second approach partitions a table using a new partitioning column (PARTITION_COLUMN). This column is populated with data using a BEFORE INSERT trigger option to generate the partitioning value for each row based on data from another column.
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS Published: 18 April 2003 |