Bookshelf Home | Contents | Index | PDF     

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

Applying Non-Additive Schema Upgrade Changes to the Target Database

Perform the following procedures to apply the non-additive 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 drop 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 dataset DSNHLQ.SIEBEL.INSTALL.JCL(SUBDRPV).
  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.
  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 dataset 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.

    For each job, 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.

    A RC=4 may be returned if a table is empty.

    NOTE:  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 8.0 schema on the target database.

To create the 8.0 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 dataset DSNHLQ.SIEBEL.INSTALL.JCL(SCHEMAT).
  4. Verify that each Unload job ran successfully.

    For each job, 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.

  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 dataset 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 in 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. 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.
  4. After submitting the job, enter cancel on the command line or press PF3 to save changes.

Executing 8.0 Index DDL and Rebuilding Indexes

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

To execute the index DDL and rebuild 8.0 indexes on the target database

  1. On the Target Database "Non-Additive" Processes Menu, select option 4: Create 8.0 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 8.0 Restructured Indexes (DDL), and press Enter.
  3. Run the job using the JCL in dataset DSNHLQ.SIEBEL.INSTALL.JCL(SCHEMAT2).

    This job runs DDL Create Index statements to build non-unique indexes for the old schema.

  4. Verify that the job ran successful. 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.
  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 8.0 Indexes, and press Enter.
  7. Run the job using the JCL in dataset DSNHLQ.SIEBEL.INSTALL.JCL(SUBNONIX).

    This job automatically submits all non-unique 8.0 index rebuild jobs.

  8. Verify that the job ran successful. 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.

Creating and Rebuilding Obsolete Indexes

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

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

To create and rebuild obsolete indexes

  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 dataset DSNHLQ.SIEBEL.INSTALL.JCL(SCHEMATO).

    This job automatically builds the old-schema obsolete indexes.

  3. Verify that the job ran successful. 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.
  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 dataset DSNHLQ.SIEBEL.INSTALL.JCL(SUBOBSIX).

    This job automatically rebuilds the old-schema obsolete indexes.

  7. Verify that the job ran successful. 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.
  8. After submitting the job, enter cancel on the command line or press PF3 to save changes.
    
Siebel Database Upgrade Guide for DB2 UDB for z/OS Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.