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

Preparing for Table Creation on the Staging Database

Upgrades: All upgrades.

Environments: All environments.

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

The PRET (pre-table) jobs are run against the staging database tables at the beginning of the upgrade; a small number of tables are altered by the PRET step to prepare the database for upgrading. There are two types of PRET jobs: jobs that you submit manually and jobs that run automatically. The manual PRET jobs perform the following tasks (this list varies according to your upgrade path):

• Determine whether there are CLOBs in the schema
• Query catalog tables for clustering index information

The automatic jobs drop some indexes, rename table(s) and add columns to tables. If you are using Siebel Scheduling, the automatic jobs use the unique job name prefixes you specify in the following procedure.

Complete the following procedures to prepare the staging database to generate unload, load, and schema files:

To run the PRET jobs

1. On the In-Place Upgrade Main Menu, select option 1:File Generation, and press Enter.
2. The Staging Database File Generation Menu appears. The panel ID is SBLSFGP.
3. Select option 4: PRET Processes. The Staging Database PRET Menu appears. The panel ID is SBLPRETP.
4. To build job cards for the PRET and pretfins job types, on the Staging Database PRET menu, select option 0: Add Jobcards & Siebel Logging, and press Enter.

   The pretfins jobcards are only built if you are upgrading a Siebel Industry Application. If you executed Household scripts on the midtier and transferred those files to the z/OS host, household jobcards are also built.

   Messages are displayed indicating the job type (PRET, pretfins, or Household), the number of jobs built and the jobcards added.

5. To load Siebel logging tables for the staging database upgrade jobs, on the Staging Database PRET Menu, select option 1: Load Siebel Log Entries (2), and press Enter.
6. Submit the job using the JCL in data set DSNHLQ.SIEBEL.INSTALL.JCL(LOADLOG3).
7. After submitting the job, review the output in SDSF or another job output facility to verify that the job ran successfully:
   1. Verify that the return code is 0 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. Verify that additional log entries have been loaded to the TMP_SBLLOG_TAR table on the staging database.
8. To run the staging PRET processes, on the Staging Database PRET menu, select option 2: PRET - PRET Jobs, and press Enter.
9. Submit the job using the JCL in data set DSNHLQ.SIEBEL.INSTALL.JCL(STGPRET).

   This triggers the first PRET job, which then automatically submits the next PRET job in sequence. The number of PRET jobs that are automatically submitted varies according to your upgrade path.

10. After submitting the job, review the output in SDSF or another job output facility to verify that the job ran successfully.

    Verify that the return code is 0 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. All jobs must complete successfully before you proceed to the next step.

11. To run the staging pretfins jobs, on the Staging Database PRET menu, select option 3: PRETF - PRET-FINS Jobs, and press Enter.

    NOTE:  You only have to perform this step if you are performing an Siebel Industry Applications (SIA) upgrade.

12. Submit the job using the JCL in data set DSNHLQ.SIEBEL.INSTALL.JCL(STGPRETF). This triggers the first PRET-FINS job, which then automatically submits the next PRET job in sequence. The number of PRET jobs that are automatically submitted varies according to your upgrade path.
13. After submitting the job, review the output in SDSF or another job output facility to verify that the job ran successfully.

    Verify that the return code is 0 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. All jobs must complete successfully before you proceed to the next step.

14. You have now completed the additive schema staging file generation process. You must now return to the midtier and restart the Siebel Upgrade Wizard to generate the nonadditive schema files, Temp table DDL files, and the load and unload files.