Bookshelf Home | Contents | Index | PDF     

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

Migrating Customizations from Development to the Target Database

NOTE:  Before you migrate your customizations from your development database to your target database, validate your storage control file. See Validating the Extracted Storage Control File.

When migrating customizations from your development source to your target database on the DB2 host, you can use one of two modes of execution:

  • Run DDL Automatically. Select this mode to apply the DDL and DML required to create the Siebel Schema directly against the database, using an ODBC connection.
  • Generate DDL Into Files. Select this mode to generate the DDL required to create the Siebel Schema into files for transfer to the DB2 host.

This section describes the DDL-generation mode of execution that is generally used under a change-management system.

If your development environment is on DB2 for z/OS, your DBA can clone the development database to the target database. For more information, see Process of Cloning a DB2 for z/OS Database.

NOTE:  Siebel 7 does not support customized database triggers. If you have created customized triggers on your Siebel base tables, disable them before migrating the database schema. You can re-create the triggers after the migration is finished.

To migrate the schema under Windows

  1. Launch the Database Server Configuration utility and follow the steps in Performing a Standard Installation Under Windows until the Siebel Database Operation screen is displayed (Step 6).
  2. Select the Migrate Repository option, and then click Next.
  3. In the Source Repository Selection Screen, choose one of the following options:
    • Read source repository directly from the database.
    • Read source repository from a previously exported file.

      If you select this option, the Repository File Selection screen is displayed. Accept the default repository migration file displayed or use the Browse button to select an alternate repository file.

      Click Next to continue.

  4. Indicate whether the target enterprise will be online or offline when migrations starts, and click Next.
  5. Specify whether or not the migration involves changes to the Siebel Schema, and click Next.
  6. On the Language Selection screen, indicate the language in which the target database runs, and click Next.
  7. Enter the name of the target database repository, for example, Siebel Repository, and click Next.
  8. In the Target RDBMS Platform screen, select IBM DB2 for z/OS, and then click Next.
  9. Enter the target database ODBC data source name and the SubSystem name, and click Next.
  10. In the Target Database User Name screen, enter your target database username and password, confirm the password by typing it again, and then click Next.
  11. In the Target Schema Qualifier screen, type the target schema qualifier in uppercase and the target group authorization ID, and then click Next.
  12. In the Migrate Repository Mechanism screen, select the Generate DDL Into Files option, and then click Next.
  13. On the DDL Commit Frequency screen, choose the number of DDL statements that can be run before a COMMIT statement is issued, and click Next.
  14. In the Output Directory screen, enter the DDL output directory and storage control file, or use the Browse button to locate these files.

    For example, specify the following for the output directory:

    DBSRVR_ROOT\db2390\dboutput\dev2prod

    and the following for the storage control file:

    DBSRVR_ROOT\db2390\my_storage_file.ctl

    Click Next.

  15. In the Log Output Directory screen, specify where log files generated during the migration are to be created, for example, DBSRVR_ROOT\db2390\dboutput\dev2prod, and click Next to continue.
  16. The runnow screen appears, giving you the choice of applying the configuration now or applying it later. To apply the configuration at any time in the future, navigate to the SIEBSRVR_ROOT\bin directory and enter the following on the command line:

    siebupg.exe /m master_dev2prod_mf.ucf

  17. Click OK and the Configuration Parameter Review screen appears.
  18. Review the parameters, and then click Finish.

    The Siebel Upgrade Wizard launches.

  19. Click OK to perform the migration.

The Siebel Upgrade Wizard creates the following files:

  • ftpsync.txt. FTPs the files that you are migrating from development to production on the DB2 host.
  • jobsync.txt. Sets up the development to production migration process on the DB2 host. Use ftpsync.txt to send this job to the mainframe.
  • unload.ldc. Unloads the control cards that are used to unload tables during the migration from development to production on the DB2 host.
  • load.ldc. Loads the control cards that are used to load tables during the migration from development to production on the DB2 host.
  • schema.sql. Applies schema changes from the schema ddl data set during the migration from development to production on the DB2 host.
  • bumpver.sql. Bumps up the Siebel Schema version during the migration from development to production on the DB2 host.

To migrate the schema under UNIX

  1. Launch the Database Server Configuration utility and follow the steps in Performing a Standard Installation Under UNIX until the Siebel Database Operation screen is displayed (Step 10).
  2. Select option 4 - Migrate Repository.
  3. On the Source Repository Selection screen, choose one of the following options:
    • Read source repository directly from the database.
    • Read source repository from a previously exported file.

      If you select this option, the Repository File Name screen is displayed. Accept the default repository migration file displayed or enter the path of an alternate repository file.

  4. Indicate whether the target enterprise will be online or offline when migrations starts.
  5. Specify whether or not the migration involves changes to the Siebel Schema.
  6. On the Language Selection screen, indicate the language in which the database runs.
  7. Enter the database ODBC data source name.
  8. Enter the database username and password.
  9. Enter the Siebel schema qualifier in uppercase.
  10. Specify the name of the source database repository, or accept the default by pressing ENTER.
  11. Specify the target database repository name, or accept the default by pressing ENTER.
  12. Specify the target database platform, in this case, select the IBM DB2 for z/OS option.
  13. Specify the target database ODBC data source name.
  14. Specify the target database DB2 subsystem name.
  15. Specify the target database username and password.
  16. Enter the target schema qualifier and the target group authorization ID.
  17. In the Installation Mechanism screen, select the Generate DDL Into a File option.
  18. On the DDL Commit Frequency screen, choose the number of DDL statements that can be run before a COMMIT statement is issued.
  19. On the DDL Output Directory screen, enter the DDL output directory name and then the name of the storage control file.

    For example, $DBSRVR_ROOT/db2390/dboutput/dev2prod and $DBSRVR_ROOT/db2390/storage.ctl, respectively.

  20. In the Common Parameters screen, specify where log files generated during the migration are to be created, for example, $DBSRVR_ROOT/db2390/dboutput/dev2prod_mf.
  21. Review the parameter values you entered, then enter 1 (Yes) to run the Siebel Upgrade Wizard (srvrupgwiz).

    You receive a message stating that the files with the Siebel Schema modifications have been generated in the DDL Output Directory. You can now apply the files on the DB2 host.

    The following files are created:

    • ftpsync.txt. FTPs the files that are migrating from development to production on the DB2 host.
    • jobsync.txt. Sets up the migration from development to production process on the DB2 host. Send this job to the mainframe using ftpsync.txt.
    • unload.ldc. Unloads control cards used to unload tables during the migration from development to production on the DB2 host.
    • load.ldc. Loads control cards used to load tables during the migration from development to production on the DB2 host.
    • schema.sql. Applies schema changes from the schema ddl data set during the migration from development to production on the DB2 host.
    • bumpver.sql. Bumps up the Siebel Schema version during the migration from development to production on the DB2 host.
    
Implementing Siebel Business Applications on DB2 UDB for z/OS