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

Applying Schema Extensions to the Development Database

After your customizations are completed, you must update your test environment.

NOTE:  Siebel Business Applications do not support customized database triggers. If you create customized triggers on your Siebel base tables, you must disable them before updating the logical database schema. You can re-create the triggers after the update is finished.

To update your local environment

1. In Siebel Tools, select the table from which you want to apply changes to the database.
2. Click Apply/DDL in the Object List Editor.
3. Select one of the following options and click OK.
   • Apply. Select this option to apply the changes you have made to the database.

     If you are connected to a local database, a message box appears, alerting you that your changes will be applied to the local database only. Click OK to continue.

   • Generate DDL. Select this option to write the DDL to implement the repository changes to a file. You can apply the DDL against the database later.

     The Apply Schema dialog box appears.

4. Fill in the fields as shown in the following table, and then click either Apply or Generate DDL, depending on the option you selected in Step 3.

   Field	Description
   Tables	Select one of the following options from the drop-down menu: All. Updates the database to reflect all changes made to the dictionary. This option forces each database object to be compared with the data dictionary, and updated if required. Current Query. Updates the database to reflect modifications made to the tables in the current query only. Current Row. Updates the database to reflect modifications made to the table in the current row only.
   Table space	Leave blank.
   16K table space	Leave blank unless you are creating a large extension table that requires a 16 KB table space.
   32K table space	Leave blank unless you are creating a large extension table that requires a 32 KB table space.
   Index space	Leave blank.
   Storage control file	Specify the complete path for the storage control file. This file is provided by the DBA and is specific to your database.
   Database user	Enter the ID of a database user with CREATEDBA or DBADM privileges. The schema qualifier is read from tools.cfg.
   Database user password	Enter the password of a database user with CREATEDBA or DBADM privileges.
   ODBC data source	Verify that the ODBC connection specified in the ODBC Data Source text box is correct for your environment. You cannot apply schema changes to any database other than the one you are currently connected to (for example, by specifying the ODBC name of a different database).
   DDL File	Specify the name and location of the file where you want the DDL to be stored (only applicable if you selected the Generate DDL option in Step 3).

   Depending on the option you selected (Apply or Generate DDL), your changes are either written directly to the database or the DDL to implement the changes is written to the file you specified.

5. To activate extensions to EIM tables, select the appropriate tables, and then click Activate.