Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS > Configuring the Database Layout >

About the Siebel Storage Control File Templates


The storage control file is unique to the DB2 UDB for OS/390 and z/OS platform for Siebel eBusiness Applications. The storage control file contains storage information (for example, partitioning indexes, table spaces, buffer pools and storage groups) that is used as the basis for the storage layout of your database. Even if you are using a preconfigured storage layout, make sure that the layout is valid for your Siebel schema.

The Siebel 7 installation process installs six storage control file templates in the DBSRVR_ROOT\DB2390 directory. Select one of the templates that follow based on your partitioning needs, your encoding scheme (if you are using partitioning), and your grouping preference.

The following storage control file templates contain partitioning schemes for a set of tables that use the ASCII encoding scheme:

  • storage_p_1to1.ctl
Every nonpartitioned table resides in its own segmented table space.
Used when you run a Standard database installation with the configuration of one table per table space with partitioning.
  • storage_p_group.ctl
Nonpartitioned tables are logically grouped by table space.
Used when you run a Standard database installation with the configuration of multiple tables per table space with partitioning.

The following storage control file templates contain partitioning schemes for a set of tables that use the EBCDIC encoding scheme:

  • storage_p_1to1_e.ctl
Every nonpartitioned table resides in its own segmented table space.

Used when you run a Standard database installation with the configuration of one table per table space with partitioning.
  • storage_p_group_e.ctl
Nonpartitioned tables are logically grouped by table space.
Used when you run a Standard database installation with the configuration of multiple tables per table space with partitioning.

The following storage control file templates contain no partitioning scheme:

  • storage_np_1to1.ctl
Provides tables in a setup where there is one nonpartitioned table in each table space.
Used when you run a Standard database installation with the configuration of one table per table space.
  • storage_np_group.ctl
Provides tables logically grouped by one table space.

Used when you run a Standard database installation with the configuration of multiple tables per table space.

The layouts of the storage control file templates are generic, and they require customization by your DBA to suit the needs of your enterprise, for example, to change the default space allocation for Siebel objects, seed data, and views.

While Siebel-provided templates might be sufficient for your development environment without any changes, your DBA needs to review and modify the database storage layout to best fit the needs of your deployment in a production environment.

The storage control file templates are the starting point for your customization process. Before you select a Siebel storage control file template, you should understand the logic behind how objects are grouped, and you should understand the object naming conventions. Knowledge of these concepts will help you when you perform customizations and will help you understand how your operations affect the underlying data sets.


 Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS 
 Published: 18 April 2003