|
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
This task is a step in the 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. 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 topic 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 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
- Launch the Database Configuration Wizard and follow the steps in Performing a Standard Installation until the Siebel Database Operation screen is displayed (Step 7).
- Select the Migrate Repository option, and click Next.
- 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.
- If you selected the Read source repository from a previously exported file option, specify the name of the source repository file you want to use, and click Next.
- Indicate whether the target database will be online or offline when the repository migration process runs against the target database, and click Next.
- 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.
- On the Language Selection screen, indicate the language in which the target database runs, and click Next.
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.
- Enter the ODBC Data Source Name to use to connect to the Siebel database, and click Next.
- Enter the database user name and password of the database in which the source repository resides, and click Next.
- 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.
- On the Repository Name screen, enter the following values, and click Next:
- Source Database Repository Name. Enter the name of the repository you are migrating. You are not prompted to enter this value if you chose the Read source repository from a previously exported file option in Step 3.
- Target Database Repository Name. Enter the name you want to assign to the repository after it is migrated.
- In the Target Database Platform screen, select IBM DB2 UDB for z/OS, and then click Next.
- Specify whether the target database you are migrating to is Unicode or non- Unicode, and click Next.
- Enter the target database ODBC data source name and the target database DB2 subsystem name, and click Next.
- 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.
- In the Target Schema Qualifier screen, type the target schema qualifier in uppercase and the target group authorization ID, and click Next.
If you indicated that there are no new schema changes to be applied (Step 6), proceed to Step 19.
- In the Migrate Repository Mechanism screen, select the Generate DDL Into Files option, and click Next.
- 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.
- In the Output Directory screen, specify values for the following:
- 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.
- Save the configuration information you have entered and launch the Siebel Upgrade wizard as described in the following topics:
- Click OK to continue.
The Siebel Upgrade Wizard creates a number of files in the directory you specified in Step 19. 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.
|
