Bookshelf Home | Contents | Index | PDF     

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

Migrating Customizations from Development to the Target Database

This topic describes how to migrate customizations from a development to a target database.

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 topic describes the DDL-generation mode of execution that is generally used under a change-management system.

This task is a step in Process of Applying Schema Extensions to the Target Database.

NOTE:  Before you migrate your customizations from your development database to your target database, validate your storage control file as described in Validating an Extracted or Modified Storage Control File.

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 Cloning a DB2 for z/OS Database.

Siebel Business Applications do 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

  1. Launch the Database Configuration Wizard and follow the steps in Performing a Standard Installation until the Siebel Database Operation screen is displayed (Step 6).
  2. Select the Migrate Repository option, and click Next.
  3. In the Source Repository Selection Screen, choose one of the following options, and click Next:
    • Read source repository directly from the database. If you select this option, proceed to Step 5.
    • Read source repository from a previously exported file. If you select this option, the Repository File Selection screen appears. Proceed to Step 4.
  4. If you selected the Read source repository from a previously exported file option, enter the name of the source repository file you want to use, and click Next.
  5. Indicate whether the target database will be online or offline when the repository migration process runs against the target database, and click Next.
  6. Select one of the following options, and click Next:
    • There are new schema changes to be applied. If you select this option, during the migration process, schema changes defined in the new repository are applied to the physical target database. The target enterprise must be offline.
    • There are no new schema changes to be applied. If you select this option, schema changes defined in the new repository are not applied to the physical target database during the migration process.
  7. On the Language Selection screen, indicate the language in which the target database runs, and click Next. (This screen is displayed only if you have more than one language deployed.)
    • If you selected the Read source repository from a previously exported file option in Step 3, proceed to Step 12.
    • If you selected the Read source repository directly from the database option in Step 3, proceed to Step 8.
  8. Enter the ODBC Data Source Name to use to connect to the Siebel database, and click Next.
  9. Enter the Database User Name for the database in which the source repository resides, and click Next.
  10. Enter the password associated with the Database User Name. Re-enter the password to confirm, and click Next.
  11. Enter the Siebel Schema Qualifier of the database in which the source repository resides. This name is a character ID that identifies the Siebel Schema owner, for example, SIEBTO.
  12. On the Source Database Repository Name screen, enter the name of the repository you are migrating, then click Next.

    You are not prompted to enter this value if you chose the Read source repository from a previously exported file option in Step 3.

  13. On the Target Database Repository Name screen, enter the name you want to assign to the repository after it is migrated, then click Next.
  14. In the Target RDBMS Platform screen, select IBM DB2 UDB for z/OS, and then click Next.
  15. Specify whether the target database you are migrating to is Unicode or non- Unicode, and click Next.
  16. Enter the target database ODBC data source name, then click Next.
  17. Enter the target database DB2 subsystem name, then click Next.
  18. In the Target Database User Name screen, enter the Target Database Username, then click Next.
  19. In the password screen, enter the password associated with the Target Database Username. Confirm the password by typing it again, then click Next.
  20. In the Target Schema Qualifier screen, type the target schema qualifier in uppercase, and then click Next.
  21. In the Target Security Group ID/Grantee screen, type the target security group authorization ID, then click Next.

    If you indicated that there are no new schema changes to be applied (Step 6), proceed to Step 25.

  22. In the Migrate Repository Mechanism screen, select the Generate DDL into Files option, and then click Next.
  23. 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.
  24. On the Output Directory screen, enter the DDL output directory. The default directory is DBSRVR_ROOT\db2390\dboutput\dev2prod (Windows) or DBSRVR_ROOT/db2390/dboutput/dev2prod (UNIX).
  25. On the Storage Control File screen, enter the name and directory path of the storage control file to be used in the migration, for example, DBSRVR_ROOT\db2390\my_storage_file.ctl (Windows) or DBSRVR_ROOT/db2390/my_storage_file.ctl (UNIX)

    Click Next.

  26. On the Log Output Directory screen, specify where log files generated during the migration are to be created, for example, SIEBSRVR_ROOT\log\dev2prod_mf (Windows) or SIEBSRVR_ROOT/log/dev2prod_mf (UNIX), and click Next to continue.
  27. Save the configuration information you have entered and launch the Siebel Upgrade wizard as described in the following relevant topic:
  28. Click OK to continue.

    The Siebel Upgrade Wizard creates a number of files in the directory you specified in Step 24. These files contain the SQL and unload and load control cards used to perform the repository migration from development to production on the DB2 host.

    A file, ftpsync.txt, is also created; use this file to transfer the migration files to z/OS where they are applied. For information on this process, see Applying Schema Changes to the Target Database.

  29. Click Exit to exit the Database Configuration Wizard.
    
Implementing Siebel Business Applications on DB2 for z/OS Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.