If you have a unique constraint or primary key set up on your table, you could change the constraint to allow for duplicate values, to get around the ORA error. Your email address will not be published. Notify me of follow-up comments by email. Notify me of new posts by email. This site uses Akismet to reduce spam. Feel free to ask questions on our Oracle forum.
Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise.
All legitimate Oracle experts publish their Oracle qualifications. Oracle technology is changing and we strive to update our BC Oracle support information. If you find an error or have a suggestion for improving our content, we would appreciate your feedback. Just e-mail: and include the URL for the page. If the issue is that the Unique Constraint can't be dropped using the Disable Constraints due to the constraint is defined using a different Owner or the Constraint is too complex then please Disable and then Re-Enable the Constraint manually.
This is Oracle's way to say ' Stop! I can't proceed or I break rules that the database owner has defined '. The Issue: There are two potential issues when masking: The masked value lookup or generated is not Unique and hence duplicated. The masked value lookup of generated is unique but it is already in the table and hence duplicated.
The Masking Engine or the user failed to disable the Unique Constraint. Select Disable Constraints in the masking job. So what is a Unique Constraint and why do we get it?
Unique Constraint This is what defines a Unique Constraint Oracle : A Unique Constraint ensures that all values in a column are unique - are different. There is this one major difference a table can have multiple Unique Constraints while it can only have one Primary Key. Is this unique to Oracle? A violation of the constraint imposed by a unique index or a unique constraint occurred. Example Unique Constraint violation example In this section, I will show two different types of Constraint Violations possible when masking a column with a Unique Constraint.
Example 1: The masked value lookup or generated is not Unique and hence duplicated. Example 2: The masked value lookup or generated is unique but it is already in the table and hence duplicated. The database error message for these two root causes is the same. Background details To visualize this, let's create an example.
0コメント