Dbms_comparison Fails When Unique Constraint Is Defined On Column
(Doc ID 1101089.1)
Last updated on JANUARY 11, 2023
Applies to:Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Information in this document applies to any platform.
When unique constraint is defined on column, DBMS_COMPARISON fails with ORA-23629 .
The index columns in a comparison must uniquely identify every row involved in a comparison. The following constraints satisfy this requirement:
* A primary key constraint
* A unique constraint on one or more non-NULL columns
In spite of having a unique constraint on "not null" column the ORA-23629 is seen.
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