Siebel Database Upgrade Guide for DB2 for z/OS > Generating the Siebel Upgrade Files >

Applying the Additive Schema Changes to the Production Staging Database

Upgrades: All upgrades.

Environments: Production test, production.

NOTE:  For development environment upgrades, all schema changes are processed as nonadditive, therefore this step is not required.

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

When you are upgrading the production staging database, you can apply all or a subset of the additive schema upgrade files ahead of the in-place upgrade. Only the additive upgrade files that you choose to apply to the staging database can be applied as additive changes to the target database before the in-place upgrade. Any additive changes you do not apply become part of the nonadditive changes that are applied later. See Applying the Nonadditive Schema Changes for further information.

NOTE:  You must rebuild tables in the target database that contain LONG VARCHAR columns before you apply additive schema changes to the production staging database. For information, see Rebuilding Target Tables Containing LONG VARCHAR Columns.

To apply additive schema changes

1. On the Staging Database Additive Schema Menu, select option 5: Select / Run Additive Changes, and press Enter.

   The Staging Pending ADDITIVE Job Submission Menus is displayed. The panel ID is SBLSADDP.

2. Choose whether you want to apply all, none, or a subset of the additive schema changes:
   • If you decide not to apply any of the additive schema changes, enter N for the Apply All (Y/N) prompt. Press PF3 until you return to the Staging Database File Generation menu.
   • To apply all of the additive schema changes, do the following:
     • Enter Y for the Apply All (Y/N) prompt, and press Enter.
     • Run the job using the JCL in data set DSNHLQ.SIEBEL.INSTALL.JCL(ADDVSCHS).
   • To apply a subset of 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.ADD.JCL(member)
     • Typing J in the Opt column for a member places you in edit mode in the JCL for the member: DSNHLQ.SIEBEL.ADD.JCL(member)
     • Typing S in the Opt column for a member places you in edit mode in the SQL for the member: DSNHLQ.SIEBEL.ADD.SQL(member)

       NOTE:  If you choose to selectively apply additive schema changes, bear in mind that some schema changes might require that other additive database, table space or table changes are applied first. In general, submit additive schema changes in database, table space, table hierarchical order.

3. Verify that the jobs ran successfully as described in Verifying JCL Upgrade Jobs.

   You can view the Siebel staging 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 5: Staging Database Joblog. See Viewing the Siebel Job Log Status for further information.

4. On the Staging Database Additive Schema Menu, select option 6: Applied / Complete on Staging, and press Enter.

   A screen is displayed that lists the status of each of the additive schema changes you applied. Do not proceed until the additive schema changes you chose to apply complete successfully. Any additive changes you do not apply become part of the nonadditive changes that are applied during the in-place database upgrade.