ALTER TABLE DROP PRIMARY KEY CONSTRAINT DOES NOT DROP UNDERLYING PK INDEX
Last updated on DECEMBER 15, 2016
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 and later
Information in this document applies to any platform.
***Checked for relevance on 15-Dec-2016***
After import of a table that contains a primary key constraint and corresponding index, a drop constraint does not drop the corresponding PK index.
When trying to insert a record into the table after dropping constraint, it fails with error
In Enterprise Manager, the index is shown as available even after dropping the constraint.
After dropping the index, we can insert the record without any violation error.
Also, if the table was to be created and not imported then the drop constraint drops the PK index also.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms