UNIQUE CONSTRAINT ERROR

Question posted by: Paul (Guest) on June 27th, 2008 07:04 PM

I have some PL/SQL code that has been running for several years and just started giving me problems. It inserts a record from one database to another going across a dblink.

It recently started giving me this error:

ORA-00001: unique constraint (SIEBEL.S_EVT_ACT_M9) violated

The problem is that SIEBEL.S_EVT_ACT_M9 is an index, but it is NOT a unique index.

When I had the problem a week ago I suspected a corrupt index, so I dropped and recreated the index. This fixed the problem. However the problem came back this week.

So now I need to get to the root cause and find out what is happening to this index.

Any help would be appreciated.

Thank you.
--
Paul LaBarbera
Oracle DBA Manager, AT&T, Morristown, NJ

Not the answer you were looking for? Post your question . . .
189,758 Experts ready to help you find a solution.
Sign up for a free account, or Login (if you're already a member).