Siebel Database Upgrade Guide > Preparing Siebel Application Data for Upgrade >

Resolving Duplicate Row IDs for a Siebel Upgrade

Upgrades from: Siebel 6.x.

Environments: Development, production test, production.

Databases: All databases.

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

During the upgrade from Siebel 6.x to 7.7.x, ROW_IDs from S_EMPLOYEE, S_CONTACT, S_ORG_INT, S_ORG_EXT, S_POSTN, and S_ORG_GROUP are inserted into S_PARTY.ROW_ID. Although row IDs are typically unique across the entire schema, there may be rare instances when row IDs are shared across these source tables.

If duplicate row IDs are not resolved before the upgrade, the upgraded S_PARTY data will be defective because there will be mismatches between the base S_PARTY record and the corresponding extension table record.

After you install the Siebel Database Server software, but before you upgrade, you must identify and resolve any duplicate row IDs in your Siebel Database.

To resolve duplicate row IDs across source tables

1. Run the script, Find_DUP_S_PARTY_ROW_IDs.sql, located in the following directory:

   WINDOWS: DBSRVR_ROOT\DATABASE_PLATFORM

   UNIX: DBSRVR_ROOT/DATABASE_PLATFORM

   This SQL script generates a list of duplicate row IDs (if any) and the tables containing the rows.

2. Choose one of the records that has a duplicate row ID.

   Choose the record with the smallest number of references to other records.

3. Copy the record.

   This creates a new record with a unique row ID.

4. Use the Merge Records command to merge the original record with the copied record.

   Records that were associated with the original record are now associated with the copied record.