Siebel Database Upgrade Guide for DB2 UDB for z/OS > Upgrading the Target Database > Performing the In-Place Target Database Upgrade >

Migrating Data On the Target Database

Perform the tasks described in this topic to migrate pre 8.0 Siebel data to version 8.0 data. Generally, this involves inserting or updating values in the target tables but new indexes may also be created and rebuilt.

There are optional data migration scripts for eChannel, Household and Product Configurator data and for Siebel Financial Services (FINS) applications. The scripts you need to apply depends on the applications you have implemented and your upgrade path. Review Table 12 to determine the scripts that apply for your upgrade.

Follow the procedure below to run each of the data migration scripts.

To run the data migration scripts

1. On the Target Database In-Place Upgrade Menu, select option 8: Data Migration Processes, and press Enter.

   The Target Database Data Migration Processes Menu appears. The panel ID is SBLDMP.

2. Select the appropriate option for the data migration script you want to run, for example, select option 3: Preschm, and press Enter, to run the preschm scripts.
3. You are placed in edit mode on one of the following datasets, depending on the option you select:
   • eChannel: DSNHLQ.SIEBEL.INSTALL.JCL(ECHANNEL)
   • Household: DSNHLQ.SIEBEL.INSTALL.JCL(HHMIG)
   • Household - FINS: DSNHLQ.SIEBEL.INSTALL.JCL(HHMIGFIN)
   • Preschm: DSNHLQ.SIEBEL.INSTALL.JCL(SUBPSH)
   • Address: DSNHLQ.SIEBEL.INSTALL.JCL(ADMIGFIN)
   • Preschm - FINS: DSNHLQ.SIEBEL.INSTALL.JCL(SUBPSHF)
   • Product Config: DSNHLQ.SIEBEL.INSTALL.JCL(SUBPC)
   • Product Config - FINS: DSNHLQ.SIEBEL.INSTALL.JCL(SUBPCF)
   • UpgISS: DSNHLQ.SIEBEL.INSTALL.JCL(SUBUPGIS)
4. Run the data migration job using the JCL in the dataset in which you have been placed. For example, if you selected option 3:Preschm, submit the JCL in the DSNHLQ.SIEBEL.INSTALL.JCL(SUBPSH) dataset.

   This job automatically submits the first job in the job stream.

   If the first Household, Preschm, and Product Configurator data migration job completes successfully, it automatically submits all subsequent jobs in the that data migration process flow. The number of jobs that are run varies according to your upgrade path.

   If one of the automatically submitted job fails, the succeeding dependent job is not submitted and the automatic job submission sequence terminates. Correct the problem that caused the job failure and resubmit the individual failed job. When the job completes successfully, it then submits the next job in sequence.

5. Verify that the job ran successfully. Review the output in SDSF or another job output facility. Verify that the RC=0 or RC=4 and that the JCLTEST return code=FLUSH. If you do not see the FLUSH return code, you can verify the condition codes by searching for the condition code IEF206I.

   NOTE:  You must fix any failed jobs before proceeding with the upgrade. For information on restarting failed jobs, see Restarting Upgrade Jobs That Fail.

6. Press PF3 to return to the Target Database Data Migration Processes Menu and run the next data migration job in sequence.

About Migrating Preschm Data

Some of the PRESCHM jobs run independently but others are submitted in a defined order and cannot run until previous jobs have completed successfully; you can run the stand-alone jobs in parallel with those with dependencies. To see the serial flow of the PRESCHM jobs and the PRESCHM job dependencies, look at the PDS member DSNHLQ.SIEBEL.PRESCHM.JCL(@DEPFLOW).

About Migrating Address Data

The Address Migration job corresponds to scripts run previously on the midtier against the target system. This means that you only need to run this job if you ran the midtier Address Migration script (rpt_dup_addr_rowids.sql) and applied the midtier procedures previously noted for rowids identified by this script. Otherwise, you do not need to run this job. For further information, see Identifying and Resolving Duplicate Row IDs.