Siebel Database Upgrade Guide > Upgrading the Siebel Database >

Identifying and Dropping Obsolete Indexes for a Siebel Upgrade

Upgrades from: All Supported Siebel releases.

Environments: Production test environment only. Does not apply to production environment.

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

Use this topic to identify indexes that may be obsolete in the Siebel Database and can be dropped. This topic is optional but is recommended since dropping obsolete indexes improves database performance.

When you run the Database Server Configuration Utilities in Prepare for Production mode, they do the following to identify obsolete indexes:

• Compares the repository schema definition in the development environment against the Siebel Database physical schema definition in the production test environment.
• If an index is present in the Siebel Database physical schema definition but not in the repository logical schema definition, the utility creates an SQL drop statement and adds it to that index. The utility places this SQL statement in a file called gen_obs_idx.sql.

You must manually review the gen_obs_idx.sql file. If it contains indexes you want to drop (those containing a drop statement not followed by a create statement), you must copy the corresponding SQL statements to another SQL file called obs_idx.sql. This file is executed by the Database Server Configuration Utilities in upgrep mode.

When the Upgrade Wizard is then run, all indexes, including obsolete indexes, are maintained during table rebuilds and data migration. The obsolete indexes file is executed during the Create Siebel Indexes step.

Prerequisites: You must have run the Database Server Configuration Utilities in Prepare for Production mode in the production test environment.

To identify and drop obsolete indexes

1. Navigate to the following file:

   Windows: DBSRVR_ROOT\platform\gen_obs_idx.sql

   UNIX: DBSRVR_ROOT/platform/gen_obs_idx.sql

   where platform is the database type, for example DB2UDB.

2. Open the file with a text editor and review the SQL statements it contains.

   The SQL statements drop indexes that are present in the Siebel Database but not in the development environment repository logical schema definition.

3. If you want to drop an index, copy the corresponding SQL statement(s) to the following file:

   Windows: DBSRVR_ROOT\platform\obs_idx.sql

   UNIX: DBSRVR_ROOT/platform/obs_idx.sql

   where platform is the database type, for example DB2UDB.

   This file will be executed when you run the Database Configuration Wizard in upgrep mode.