Dropping Partitioned EIM Tables

During the target database upgrade, EIM tables are dropped after additive changes are applied to the database and are later re-created when the nonadditive schema changes are applied to the database.

When a partitioned EIM table is dropped, however, the table space is also dropped. Because table space creation is considered an additive change, the upgrade attempts to create EIM table spaces for partitioned EIM tables when other additive changes are applied to the target database, that is, before the partitioned EIM tables and related table spaces have been dropped.

To avoid processing errors during the target database upgrade, therefore, you must manually change the sequence in which partitioned EIM tables are dropped. Drop partitioned EIM tables before you apply additive schema changes to the target database.

The following procedure describes how to change the sequence in which partitioned EIM tables are dropped.

To drop partitioned EIM tables

1. Run the sample code listed in Sample Code for Generating a List of Table Spaces to Drop to generate a list of the table spaces that contain partitioned EIM tables.

   A DROP command is also generated for each of the table spaces.

2. Run the generated DROP commands against the target database before you apply additive schema updates.

   The table spaces are re-created when you apply additive upgrade changes to the database.

3. Edit the data set SIEBEL.INSTALL.JCL(INFDRPT) and delete the steps that drop the table spaces containing partitioned EIM tables, that is, delete the steps that drop the table spaces you previously dropped in Step 2.

   The data set SIEBEL.INSTALL.JCL(INFDRPT) is run as part of the process of Preparing the Target Database for the Upgrade.