Bookshelf Home | Contents | Index | PDF     

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

Applying Nonadditive Schema Upgrade Changes to the Target Database

Perform the following procedures to apply the nonadditive schema upgrade changes to the target database. Perform the procedures in the sequence in which they are listed.

Removing Target Database Views

Perform the following procedure to remove views from the target database.

To remove views from the target database

  1. On the Target Database In-Place Upgrade Menu, select option 5: Non-Additive Processes, and press Enter.

    The following message appears:

    Before proceeding, make sure ALL "Pret-FINS" jobs completed. Re-enter option 5 to continue.

  2. Reselect option 5: Non-Additive Processes, and press Enter.

    The Target Database "Non-Additive" Processes Menu appears. The panel ID is SBLNONP.

  3. Select option 0: Drop Views, and press Enter.
  4. Run the job using the JCL in data set DSNHLQ.SIEBEL.INSTALL.JCL(SUBDRPV).
  5. Verify that the job ran successfully with a return code of 0 or 4. For information, see Verifying JCL Upgrade Jobs.
  6. After submitting the job, enter cancel on the command line or press PF3 to save changes.

Running Unload Jobs on the Target Database

Perform the following procedure to run unload jobs on the target database.

To run unload jobs on the target database

  1. On the Target Database "Non-Additive" Processes Menu, select option 1: Unload Schema, and press Enter.
  2. Run the job using the JCL in data set DSNHLQ.SIEBEL.INSTALL.JCL(SUBUNLD).

    This job submits all the Unload jobs to run in parallel. The number of Unload jobs run varies according to your upgrade path.

  3. Verify that each Unload job ran successfully.
    • Verify that each job ran successfully with a return code of 0. For information, see Verifying JCL Upgrade Jobs.
    • Review unload jobs that generate a return code of 4. A return code of 4 might be returned if a table is empty but it can also indicate that an unload job has failed as a result of DSNTIAUL utility CCSID conversion errors. For additional information, see About DSNTIAUL CCSID Conversion Errors.

      If the DSNTIAUL utility encounters an unload job that generates a CCSID conversion error, it generates a return code of 4 and stops the unload process at that point. Exit from the upgrade process and use a program, such as the IBM DB2 UNLOAD utility, to complete the load and unload processing.

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

  4. After submitting the job, enter cancel on the command line or press PF3 to save changes.
  5. View the job status log.

    You can view the job status log by completing the procedure described in Running SQL in Siebel Logs.

Creating the Schema on the Target Database

Perform the following procedure to create the Siebel CRM schema for the current release on the target database.

To create the Siebel CRM schema on the target database

  1. On the Target Database "Non-Additive" Processes Menu, select option 2: Create Schema, and press Enter.

    The following message appears:

    Before proceeding, make sure ALL "UNLOAD" jobs completed. Re-enter option 2 to continue.

  2. Reselect option 2: Create Schema, and press Enter.
  3. Run the job using the JCL in data set DSNHLQ.SIEBEL.INSTALL.JCL(SCHEMAT).
  4. Verify that each job ran successfully with a return code of 0 or 4. For information, see Verifying JCL Upgrade Jobs
  5. After submitting the job, enter cancel on the command line or press PF3 to save changes.

Loading the Schema on the Target Database

Perform the following procedure to run Load jobs on the target database.

To run the Load jobs on the target database

  1. On the Target Database "Non-Additive" Processes Menu, select option 3: Load/Re-Load Schema, and press Enter.
  2. Run the job using the JCL in data set DSNHLQ.SIEBEL.INSTALL.JCL(SUBLOAD).

    This submits all the Load jobs to run in parallel. The number of upgrade Load jobs varies by upgrade path.

    NOTE:  If your database layout allows multiple tables for each table space, Loads for the same table space are stacked in the input job queue using the same job name to guarantee serialized loading.

  3. Verify that the job ran successfully with a return code of 0 or 4. For information, see Verifying JCL Upgrade Jobs.
  4. After submitting the job, enter cancel on the command line or press PF3 to save changes.

Executing Index DDL and Rebuilding Indexes

Perform the following procedure to execute the index DDL for Siebel CRM, and to rebuild indexes on the target database.

To execute the index DDL and to rebuild indexes

  1. On the Target Database "Non-Additive" Processes Menu, select option 4: Create Restructured Indexes (DDL), and press Enter.

    The following message appears:

    Before proceeding, make sure ALL "LOAD" jobs completed. Re-enter option 4 to continue.

  2. Reselect option 4: Create Restructured Indexes (DDL), and press Enter.
  3. Run the job using the JCL in data set DSNHLQ.SIEBEL.INSTALL.JCL(SCHEMAT2).

    This job runs DDL Create Index statements to build nonunique indexes for the old schema.

  4. Verify that the job ran successfully with a return code of 0 or 4. For information, see Verifying JCL Upgrade Jobs.
  5. After submitting the job, enter cancel on the command line or press PF3 to save changes.
  6. On the Target Database "Non-Additive" Processes Menu, select option 5: Rebuild Indexes, and press Enter.
  7. Run the job using the JCL in data set DSNHLQ.SIEBEL.INSTALL.JCL(SUBNONIX).

    This job automatically submits all nonunique 8.1 and 8.2 index rebuild jobs.

  8. Verify that the job ran successfully with a return code of 0 or 4. For information, see Verifying JCL Upgrade Jobs.

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

Creating and Rebuilding Obsolete Indexes

If you choose, you can create and rebuild the old schema obsolete indexes. This step is optional.

The procedure to create and rebuild obsolete indexes differs, depending on whether you perform this task during the target database upgrade process, or after you have completed the target database upgrade (recommended). Both procedures are described in this topic.

Perform the following procedure to create and rebuild obsolete indexes on the target database during the target database upgrade process.

To create and rebuild obsolete indexes during the database upgrade

  1. On the Target Database "Non-Additive" Processes Menu, select option 6: Create Obsolete Indexes, and press Enter.
  2. Run the job using the JCL in data set DSNHLQ.SIEBEL.INSTALL.JCL(SCHEMATO).

    This job automatically builds the old-schema obsolete indexes.

  3. Verify that the job ran successfully with a return code of 0 or 4. For information, see Verifying JCL Upgrade Jobs.
  4. After submitting the job, enter cancel on the command line or press PF3 to save changes.
  5. On the Target Database "Non-Additive" Processes Menu, select option 7:Rebuild Obsolete Indexes, and press Enter.
  6. Run the job using the JCL in data set DSNHLQ.SIEBEL.INSTALL.JCL(SUBOBSIX).

    This job automatically rebuilds the old-schema obsolete indexes.

  7. Verify that the job ran successfully with a return code of 0 or 4. For information, see Verifying JCL Upgrade Jobs.
  8. After submitting the job, enter cancel on the command line or press PF3 to save changes.

Perform the following procedure to create and rebuild obsolete indexes on the target database after the target database upgrade is completed.

To create and rebuild obsolete indexes after the database upgrade is completed

  1. To create the obsolete indexes, run the SQL in the DSNHLQ.SIEBEL.DDLOIND data set.
  2. Verify that the jobs ran successfully with a return code of 0. For information, see Verifying JCL Upgrade Jobs.
  3. Review the list of obsolete indexes created; rebuild only those indexes that you require.
  4. Rebuild the obsolete indexes by submitting the appropriate JCL in the DSNHLQ.SIEBEL.OBSIX.JCL data set.

    The control cards for the rebuild index jobs are located in the DSNHLQ.SIEBEL.OBSIX.SQL data set.

  5. Verify that the jobs ran successfully with a return code of 0. For information, see Verifying JCL Upgrade Jobs.
      
Siebel Database Upgrade Guide for DB2 for z/OS Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices.