Siebel Database Upgrade Guide for DB2 UDB for z/OS > Creating the Siebel Staging Database >

Removing Interface Tables and Triggers

Once you have build the staging database and prepared the upgrade environment on the z/OS host, the final task to complete before you generate the upgrade files is to remove triggers and EIM/Interface tables from the staging database. The following procedure describes this task.

To remove EIM/Interface tables and triggers from the staging database

1. On the Staging Database Environment Setup Menu, select option 6: PREGEN Processes, and press Enter.

   The Staging Database Pre_Gen Maint. Menu is displayed. The panel ID is SBLPREGP. Options on this panel allow you to generate EIM DROP statements, identify tables with CLOB columns, and generate trigger drops.

2. Select option 0: Generate EIM/Interface Table/Tablespace Drops, and press Enter.
3. Submit the JCL in the data set DSNHLQ.SIEBEL.pregen.jcl (PREGEN1). This job generates the EIM, Interface table, and table space DROP statements.
4. 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.

5. After submitting the job, enter cancel on the command line or press PF3 to save changes.
6. On the Staging Database Pre_Gen Maint. Menu, select option 1. Generate: - List of Tables with CLOB columns - Trigger Drops, and press Enter.
7. Submit the JCL in the data set DSNHLQ.SIEBEL.pregen.jcl (PREGEN2). A list of trigger drops and tables with CLOB columns is generated.
8. 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.
9. After submitting the job, enter cancel on the command line or press PF3 to save changes.
10. On the Staging Database Pre_Gen Maint. Menu, select option 2. Generate: Report of Address Duplicate Rowids, and press Enter.

    NOTE:  You need to select this option to run jobs to generate a report of duplicate address row IDs only if you are upgrading from SIA 6.2.1 or FINS 7.0.4.

11. Submit the JCL in the data set DSNHLQ.SIEBEL.pregen.jcl (ADROWIDS) to generate a report of duplicate address row IDs.

    For further information on upgrading address data, see the chapter on preparing application data for upgrade in Siebel Database Upgrade Guide.

12. 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.
13. After submitting the job, enter cancel on the command line or press PF3 to save changes.
14. On the Staging Database Pre_Gen Maint. Menu, select option 3: Update Address Report generated log entry, and press Enter.

    NOTE:  You need to select this option to update address report log entries only if you are upgrading from SIA 6.2.1 or FINS 7.0.4.

15. Submit the JCL in the dataset DSNHLQ.SIEBEL.pregen.jcl (ADRLOGS) to update address report log entries.
16. 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.
17. After submitting the job, enter cancel on the command line or press PF3 to save changes.
18. Press PF3 to return to the Staging Database Environment Setup Menu.
19. Select option 7: Drop Interface Tables, and press Enter.
20. Submit the JCL in the dataset DSNHLQ.SIEBEL.install.jcl (PRETIDRP) to drop EIM and Interface tables from the staging database.
21. 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.
22. After submitting the job, enter cancel on the command line or press PF3 to save changes.

This completes the process of creating a staging database. You can now generate the upgrade files.