Implementing Siebel Business Applications on DB2 UDB for z/OS > Understanding Siebel Partitioning >

Example of Partitioning the S_ADDR_ORG Table

You can use the Siebel-selected partitioned tables exactly as they are shipped in Siebel 8.0. You can also customize the Siebel partitioned tables, or partition other Siebel schema base tables. For information on customizing the partitioned tables or partitioning nonpartitioned tables, see Partitioning Tables and Indexes Using the Database Storage Configurator.

This topic gives one example of how to partition a table and a table space. The example definitions in this topic reflect a partitioning scenario for the S_ADDR_ORG table, which resides in the H0401504 partitioned table space. The Siebel partitioning template used for this scenario is the storage_p_e.ctl storage control file.

In a storage control file, the partitioned table space is defined with two types of storage control file objects: Tablespace and Tspart (table space partitions). The storage control file objects related to partitioning are:

  • Tablespace
  • Tspart (table space partitions)
  • Table
  • PartitionBase (defines the partitioning key for table-controlled partitioned tables)
  • PartitionPart (defines the key value ranges used for partitioning data for table-controlled partitioned tables)
  • IndexBase (base definition of a partitioning index)
  • IndexPart (index partitions)

A table definition always includes the same options, whether the corresponding table space is partitioned or not. However, the table space, partition and index objects include different options, depending on whether the table space is partitioned or nonpartitioned.

NOTE:  The object numbers that identify the objects in this example might differ in your implementation.

Implementing Siebel Business Applications on DB2 UDB for z/OS Copyright © 2008, Oracle. All rights reserved.