Siebel Database Upgrade Guide for DB2 for z/OS > Upgrading the Target Database >

Applying Additive Upgrade Changes to the Target Database

Upgrades: All upgrades.

Environments: Production test, production.

This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.

NOTE:  For development database upgrades, all schema changes are processed as nonadditive so this step does not apply.

Before you can perform the in-place target database upgrade, you must first apply all of the additive schema changes that you previously applied to the production staging database to the production target database. See Applying the Additive Schema Changes to the Production Staging Database for further information.

When applying additive changes, you can either:

• Apply one, or a few of the additive changes to the target database during one or more sessions.
• Apply all of the additive changes as one job, provided that you applied all of the additive changes to the staging database.

Both methods of applying additive changes are described in this topic.

Applying Additive Changes Individually

You can apply individual additive changes to the target database using the following procedure.

To apply selected additive changes to the target production database

1. If you are not on the Siebel Upgrade Main Menu, enter the following command:

   TSO SBLUPG81

2. Select option 2: Target Database Processes - Pre-Upgrade, and press Enter.
3. Select option 1: Schedule/Run PENDING Jobs (Target), and press Enter.

   The Target Additive PENDING Job Status Menu is displayed. The panel ID is SBLSADTP.

   This panel lists all the pending additive jobs, that is, all the jobs that were applied as additive jobs to the staging database and which have not been applied to the target database.

4. To apply or view the additive schema changes, enter either J, S, or SUB in the Opt column of the appropriate member, and press Enter:
   • Typing SUB in the Opt column for a member automatically submits the JCL to apply the additive change in the member: DSNHLQ.SIEBEL.ADDTAR.JCL(member)

     To apply all the additive changes together, follow the procedure in Applying the Additive Changes in One Job.

   • Typing J in the Opt column for a member places you in edit mode in the JCL for the member: DSNHLQ.SIEBEL.ADDTAR.JCL(member)
   • Typing S in the Opt column for a member places you in edit mode in the SQL for the member: DSNHLQ.SIEBEL.ADDTAR.SQL(member)

     NOTE:  You can selectively submit additive schema changes according to the amount of time you have available. You must bear in mind, however, that some schema changes might require that other additive database, table space or table changes are applied first. Review the additive changes before submitting them and, in general, submit additive schema changes in database, table space, table hierarchical order.

5. After submitting the JCL to apply the additive change in a member, verify that the job ran successfully:
   1. Review the output in SDSF or another job output facility very carefully. Verify that the return code is 0, 4, or 8 and that the JCLTEST return code is FLUSH. If you do not see the FLUSH return code, you can verify the condition codes by searching for the condition code IEF206I.
   2. You can view the Siebel target database job log to check whether an additive job completed successfully or not by navigating to the In-Place Upgrade Main Menu and selecting option 6: Target Database Joblog. See Viewing the Siebel Job Log Status for further information.

      Do not proceed until all the pending additive schema jobs are run successfully.

Applying the Additive Changes in One Job

You can apply all the additive schema upgrade changes to the target database using the JCL in the data set DSNHLQ.SIEBEL.INSTALL.JCL(ADDVSCHT) provided you also applied all of the additive changes to the staging database using the JCL in the DSNHLQ.SIEBEL.INSTALL.JCL(ADDVSCHS) data set.

CAUTION:  If you applied only a subset of the additive schema upgrade changes to the staging database, you must not apply the additive schema upgrade changes to the target database using the JCL in the data set DSNHLQ.SIEBEL.INSTALL.JCL(ADDVSCHS). If you do, you will corrupt the target database.

To apply all additive changes to the target production database

1. Navigate to the ISPF Primary Option Menu, and select option 2: Edit.
2. Specify DSNHLQ.SIEBEL.INSTALL.JCL(ADDVSCHT) as the name of the data set member you want to edit on the Edit Entry Panel.
3. Submit the job in the ADDVSCHT member.

   All of the additive schema changes are automatically submitted and applied to the target database.

   NOTE:  You must choose to either apply all of the additive changes in one job, or apply them all individually. If you apply any of the additive changes to the target database individually, as described in Applying Additive Changes Individually, you cannot use the DSNHLQ.SIEBEL.INSTALL.JCL(ADDVSCHT) member to apply additive changes; attempting to do will cause an error in your upgrade.

4. To ensure performance is not adversely affected when additive changes are applied in one job using the ADDVSCHT member, all of the indexes are created using the DEFINE YES, DEFER YES syntax. After applying the additive changes, you can rebuild the indexes for each index created by the ADDVSCHT member by submitting the JCL in the DSNHLQ.SIEBEL.EXEC(@ADDIX) data set.

   You can submit the index rebuild jobs all together, or individually. To submit the rebuild index jobs in one step:

   1. Navigate to the ISPF Primary Option Menu, and select option 3.4.
   2. On the Data Set List Utility (DSLIST) panel, type EXEC on the line next to the @ADDIX member. Press Enter.

      All of the rebuild index jobs are submitted.

      To submit each index rebuild job individually:

   • Edit the DSNHLQ.SIEBEL.EXEC(@ADDIX) member by typing e to the left of the member name. Press Enter.
   • Select the job you want to run, type submit on the command line, and press Enter.

     The rebuild index job is submitted.