Implementing Siebel Business Applications on DB2 for z/OS > Customizing a Development Environment > Roadmap for Creating Custom Extensions to the Siebel Schema >

Amending the Storage Control File for New Schema Objects

If you need to create new database objects as a result of changes made to the Siebel Schema in Siebel Tools, you must create a storage definition for the new objects in your storage control file. If you do not create storage control file definitions for new objects, the required objects are created using values derived from the Defaults object in the storage control file when you apply the schema extensions to the development database using Siebel Tools.

This task is a step in Roadmap for Creating Custom Extensions to the Siebel Schema.

NOTE:  If you have different storage control files for your development environment and production environment, you must add the new object definitions to both storage control files.

Use the following procedure to add new object definitions to a storage control file.

To amend the storage control file for new schema objects

1. Using the Extract from catalog option on the Database Configuration Wizard, extract the storage control file from the Siebel Schema that is being extended.

   For information on this task, see Extracting a Storage Control File from the DB2 Catalog.

2. Add the new object definitions to the extracted storage control file. For example, if you create a new extension table, you must create a table object definition, and object definitions for the database and table space in which the table is to be placed.

   You can edit the storage control file using a text editor or you can use the Siebel Database Storage Configurator to edit the file. For additional information, see Using the Siebel Database Storage Configurator.

   You can add new object definitions anywhere in the storage control file, for example, you can append them to the end of the file. The new object definitions are read from the file when you apply the physical schema extensions to the development database. Once the new objects are physically created in the Siebel Schema, the next time the Extract from catalog task is run to produce a new storage control file, these objects are correctly grouped by type in the file.

   NOTE:  The Extract from catalog process collects the definition for only Siebel Schema database and table space objects that are associated with a table.

   The following example shows object definitions for a new extension table, named X_EXTENT, which is created in a table space, named S0600100, which is in a database, named SIDB6001:

   [Object 6001]
   Type = Database
   Name = SIDB6001
   LockSize = Page

   [Object 6002]
   Type = Tablespace
   Name = S0600100
   Database = SIDB6001
   LockSize = Page
   Bufferpool = BP16K1
   Define = No
   Partitions = 0

   [Object 6003]
   Type = Table
   Name = X_EXTENT
   Database = SIDB6001
   Tablespace= S0600100
   CLOBS = NO

   When specifying the object number, for example [Object 6001], enter the next number in sequence after the last object number listed in the existing storage control file.