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

About the Siebel Database Server File Installation

The Siebel Database Server file installation process uses two types of Siebel control files:

• DDL control file. The DDL control file contains the logical definitions for all Siebel tables and indexes for the current version of the Siebel eBusiness Application. The DDL control file (ddl.ctl or schema.ddl) is read-only to protect the integrity of the Siebel data model.
• Storage control file. The storage control file contains the physical database layout. The storage control file is specific to DB2 UDB for z/OS and OS/390.

  Carefully review the storage control file (or the resulting schema.sql file that is based on the storage control file) and adjust the database layout to satisfy your database requirements. You can modify any option available for each database object, for example, by fine-tuning FREEPAGE and PCTFREE for a particular table space or a group of table spaces.

  CAUTION:  It is especially important that you review SEGSIZE, PRIQTY, and SECQTY for the table spaces that will contain the major tables for your implementation. Siebel Systems has appropriately sized the table spaces used for Siebel repository tables, but because sizing requirements for base Siebel tables vary from deployment to deployment, it is your responsibility to set storage parameters capable of accommodating your installation.

Together, the DDL control file and the storage control file provide Siebel eBusiness Applications with all the information necessary to create DDL for the Siebel schema in an output file (by default named schema.sql).

There are two methods you can use to execute the SQL files from a designated Siebel Server:

• Method 1. Automatic execution from Siebel Server using an ODBC utility (such as odbcsql from Siebel Systems) or a version control tool for file execution. To use this method, review Configuration Options for DB2 Connect to determine the configuration appropriate to the Client your enterprise supports, then follow the instructions in Installing Required IBM Fix Packs.
• Method 2. Direct execution on DB2 host using Siebel-provided scripts, your own FTP, or any other file transfer program to transfer files to DB2 host, then use a native IBM utility such as SPUFI for file execution. This method is outside the scope of this guide. If you want to execute SQL using mainframe native tools, refer to IBM documentation.