Re: Help: how to interpret constraint errors?

From: Bob Leonard <farsider_at_postoffice.ptd.net>
Date: 1996/08/07
Message-ID: <4u8sjl$4h5_at_news2.ptd.net>#1/1


Ther are two tables to look in to determine the problem, user_constraints and user_cons_columns. Have a look around those filtering on constraint_name and you can determine the column and table that the value is being matched to.

Bob Leonard
In article <michel.lalonde.85.0009B364_at_sit.ulaval.ca>, michel.lalonde_at_sit.ulaval.ca says...
>
>In article <32027583.766D_at_concentric.net> Alastair Gregory
 <agregory_at_concentric.net> writes:
>>From: Alastair Gregory <agregory_at_concentric.net>
>>Subject: Help: how to interpret constraint errors?
>>Date: Fri, 02 Aug 1996 17:39:15 -0400
 

>>Hello, Oracle gurus!
 

>>Can anyone tell me how to take an ORACLE 7 error message
>>such as
 

>>ORA-02291: integrity constraint (userid.SYS_C002776) violated -
>>parent key not found
 

>>and map the code SYS_C002776 back to identify which field
>>(in the table being inserted into) is the one which fails
>>the constraint check, and which table holds the (missing)
>>parent record? I know the answer is somewhere in the system
>>tables, but I don't know enough about them :
>
>We name all our constraints so we dont have any SYS_C... errors
>
>EX: for a foreign key our standard is FK_TABLE1_TABLE2 so the message
>will be:
>
>integrity constraints (userid.FK_TABLE1_TABLE2)
>
>So we know what is the problem.
>the source and the
Received on Wed Aug 07 1996 - 00:00:00 CEST

Original text of this message