Implementing Siebel Business Applications on DB2 UDB for z/OS > Customizing a Development Environment > Process of Applying Schema Extensions to the Target Database >

Synchronizing the Repository and the Physical Schema

To synchronize the Siebel repository database definitions and the existing physical Siebel database, use the Synchronize Schema Definition option of the Database Configuration Wizard.

When you synchronize repository definitions and the existing Siebel Schema, the following data sources are accessed:

• Siebel Repository
• Storage control file
• DB2 catalog

When you run the Synchronize Schema Definition option, be aware of the following:

• Custom columns in the Siebel Schema that are not in the Siebel Repository are not deleted
• Custom indexes in the Siebel Schema that are not in the Siebel Repository are deleted

NOTE:  It is recommended that you issue an SQL DROP command to remove EIM tables from the database before synchronizing the Siebel logical and physical schemas to ensure that the synchronization process does not fail when processing EIM tables.

To synchronize Siebel schema definitions

1. Launch the Database Configuration Wizard and follow the steps in Performing a Standard Installation until the Siebel Database Operation screen (Step 7) is displayed.
2. Select the Run Database Utilities option, and click Next.
3. Select the Synchronize Schema Definition option, and click Next.
4. Identify the appropriate database encoding method, and click Next.
   • UNICODE Database
   • Non-UNICODE Database

     If you selected the UNICODE Database option, proceed to Step 6.

5. Specify the code page encoding scheme for your Siebel Database, either ASCII or EBCDIC, and click Next.
6. On the Language Selection screen, select the language in which the database runs, and click Next.
7. Enter the ODBC data source name to use to connect to the database and the source database DB2 subsystem name, and click Next.
8. Enter the database user name and password, and then enter the password again to confirm it. Click Next.
9. Specify the Siebel Schema qualifier in uppercase and the security group ID, and click Next.
10. Specify the Repository Synchronization Mechanism, in this case, select the Generate DDL into Files option, and click Next.
11. On the Commit Frequency screen, choose the number of DDL statements that can be run before a COMMIT statement is issued, and click Next.
12. Enter the name of the output directory where the DDL is to be created, and enter the path and name of the storage control file to use in the synchronization process. Alternatively, use the Browse button to locate these files.

    By default, the DDL output directory is DBSRVR_ROOT\db2390\dboutput\ddlsync (Windows) or DBSRVR_ROOT/db2390/dboutput/ddlsync (UNIX). Click Next.

13. Enter the name of the Repository with which the existing Siebel database is to be synchronized. Click Next.
14. Enter the name of the directory where the log files are to be created, and click Next. By default, the files are created in SIEBSRVR_ROOT\log\ddlsync_mf (Windows) or SIEBSRVR_ROOT/log/ddlsync_mf (UNIX).
15. Save the configuration information you have entered and launch the Siebel Upgrade wizard as described in the following topics:
    • Running the Database Configuration Wizard Under Windows
    • Running the Database Configuration Wizard Under UNIX
16. Click OK and the Wizard generates the DDL required to synchronize the Siebel Database and the Siebel Repository.
    • If you selected the Run DDL Automatically installation option, the Siebel Upgrade Wizard applies the DDL commands to synchronize the Siebel Database with the Repository directly against the database on the z/OS host. When you receive a message stating that the configuration was applied successfully, click OK.

      This step completes the Run DDL Automatically synchronization option.

    • If you selected the Generate DDL Into Files installation option, the Siebel Upgrade Wizard generates the following files into the output directory that you designated in Step 14 after the synchronize schema definition configuration is completed:
      • schema.sql
      • ddlview.sql

        NOTE:  If no files are generated, it means that the Siebel logical and physical schema definitions are the same.

17. Ask your DBA to apply these files to synchronize the Siebel repository database definitions with the existing physical Siebel database.