Configuring Siebel eBusiness Applications > Configuring Tables and Columns >

Applying Database Extensions to the Local Database

After you have extended the logical schema, by adding columns or tables for example, you must apply those changes to the local database.

NOTE:  Siebel eBusiness Applications version 7 do not support customized database triggers. If you have created customized triggers on your Siebel base tables, you must disable them before updating the logical database schema. You will then need to recreate the triggers after the update is finished.

This task is part of the Select Edit > New Record to specify each column to add to the index..

To update your local environment

1. In the Object Explorer, select the table from which you want to apply changes to the database.
2. Click Apply in the Object List Editor.

   A dialog box appears, alerting you that you are about to connect to a local database and asking if you want to continue.

   NOTE:  The Apply button is disabled for tables of type External. For more information about external tables, see Overview: Siebel eBusiness Application Integration Volume I.

3. Click OK.

   The Apply Schema dialog box appears.

4. Fill in the fields as shown in the following table, and then click Apply.

   NOTE:  When applying changes, the Privileged User Id must be the tableowner name. For example, suppose your login Id is JSMITH and password is DB2. When you apply schema changes to the local database, your Privileged User Id/Password would be SIEBEL/DB2.

   Field	Description
   Tables	Select one of the following options from the drop-down menu: All. Update 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. Update the database to reflect modifications made to the tables in the current query only. Current Row. Update the database to reflect modifications made to the table in the current row only.
   Table space	Leave blank.
   16K table space	Leave blank.
   32K table space	Leave blank.
   Index space	Leave blank.
   Table groupings file	Optional. This file is provided by the DBA and is specific to your database.
   Privileged user id	Enter your database user ID, typically SIEBEL. The table owner is read from tools.cfg.
   Privileged user password	Enter your database user password, for example SADMIN. The password is case sensitive and should be all in uppercase. For example, suppose the mobile user JSMITH initialized the local database, he used DB2 as the password. Then when he applies schema changes to the local database, he should use SIEBEL/DB2 as the Privileged User Id/Password pair. When the database initialization for a mobile client is performed, the table owner changes from SIEBEL to the mobile user's password. In this case, use the mobile user's password in the password field.
   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).

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

   Your extension tables and columns are now available to use in your configuration.