My Oracle Support Banner

Siebel Database Upgrade Fails with Error An explicit DROP INDEX is not allowed on index 'CX_ACC_BILM_REL.CX_ACC_BILM_REL_P1'. It is being used for PRIMARY KEY constraint enforcement. (Doc ID 3048008.1)

Last updated on SEPTEMBER 17, 2024

Applies to:

Siebel CRM - Version 24.3 and later
Information in this document applies to any platform.

Symptoms

When attempting to run the Siebel Database Upgrade (IRM) in the production mode, it fails while processing tables logical and physical synchronization as follows:

upgrep_prod_<source_version>\output\ddlctl_tab.log:

drop index CX_ACC_BILM_REL.CX_ACC_BILM_REL_P1

2024-09-08 11:03:34 [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]An explicit DROP INDEX is not allowed on index 'CX_ACC_BILM_REL.CX_ACC_BILM_REL_P1'. It is being used for PRIMARY KEY constraint enforcement.

2024-09-08 11:03:34 SQL Statement:
alter table CX_ACC_BILM_REL alter column "ROW_ID"  nvarchar(15)         not null

2024-09-08 11:03:34[Microsoft] [ODBC Driver 18 for SQL Server][SQL Server]The object 'CX_ACC_BILM_REL_P1' is dependent on column 'ROW_ID'.



The following steps can be executed:

1. Run the Siebel Database Configuration Wizard, choose Upgrade, Product Environment, and the other necessary parameters. The whole process execution can be found in Siebel Database Upgrade Guide > Performing a Siebel Incremental Repository Merge.
2. At the end of the wizard, execute the upgrade.


Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.