Constraint definition

hello,
Can someone please point me what is wrong with this constratint definition. (running against Oracle 10g)
ALTER TABLE point.NOTEBLOB ADD CONSTRAINT FK_NOTEBLOB
FOREIGN KEY (PRIMARYKEY) REFERENCES point.NOTES (PRIMARYKEY)
ON DELETE CASCADE
if i changed i to the follwoing, it works,
ALTER TABLE "POINT"."NOTEBLOB" ADD ( CONSTRAINT "FK_NOTEBLOB" FOREIGN KEY ("PRIMARYKEY") REFERENCES "POINT"."NOTES" ("PRIMARYKEY") VALIDATE )
any help will be greatly appreciated.
regards
Tabassum

sigh what error message do you get with the first formulation? It makes it a lot easier to diagnose the problem if we know what it actually is. I could guess but I'm not going to. Maybe somebody else will.
Please help us to help you.
Regards, APC

Similar Messages

  • IMP-00093: Inconsistency between dumpfile constraint definition for table

    I am getting the following error while importing table. I have checked and I can see the table and constraint exist.
    Anyone know in what situition this warning will be trigger out? Will this warning give any impact to the table or database ? any solutions?
    Export file created by EXPORT:V09.02.00 via conventional path
    import done in US7ASCII character set and AL16UTF16 NCHAR character set
    . importing PROD_USR's objects into PROD_USR
    . . importing table "FLPBABA" 29 rows imported
    IMP-00093: Inconsistency between dumpfile constraint definition for table FLPBABA with columns ("FQ_FLPBABA_UPD_TMS" , "F9_FLPBABA_B4_AFTER")
    Import terminated successfully with warnings.
    Message was edited by:
    cocorico78

    The full error message might explain a little.
    Oracle Error :: IMP-00093
    Inconsistency between dumpfile constraint definition for table string with columns (string)
    Cause
    Import failed to locate a base table for a constraint that was defined in the dump file and statistics were not imported.
    Action
    Check to see if the table and constraint exist. If the table and constraint exist, then report this to Oracle Support Services as an Import internal error.

  • NULLABLE column is not updated after the NOT NULL constraint definition...

    Hi,
    SQL> select column_name,nullable from all_tab_columns where table_name='EMP';
    COLUMN_NAME                    NULLABLE
    EMPNO                          N
    ENAME                          Y
    JOB                            Y
    MGR                            Y
    HIREDATE                       Y
    SAL                            Y
    COMM                           Y
    DEPTNO                         Y
    CODE_POLEIS_DIAM               Y
    9 rows selected
    SQL> ALTER TABLE EMP add constraint emp_job_nn check(job is not null);
    Table altered
    SQL> select constraint_name from all_cons_columns
      2  where table_name='EMP';
    CONSTRAINT_NAME
    FK_DEPTNO
    PK_EMP
    EMP_JOB_NN
    SQL> select column_name,nullable from all_tab_columns where table_name='EMP';
    COLUMN_NAME                    NULLABLE
    EMPNO                          N
    ENAME                          Y
    JOB                            Y                         <---------'NULL'
    MGR                            Y
    HIREDATE                       Y
    SAL                            Y
    COMM                           Y
    DEPTNO                         Y
    CODE_POLEIS_DIAM               Y
    9 rows selected
    Why is not updated....????
    In Oracle ebook:
    Oracle® Database Reference
    10g Release 2 (10.2)
    Part Number B14237-02
    the comments about the NULLBLE column are as follows:
    "Specifies whether a column allows NULLs. Value is N if there is a NOT NULL constraint on the column or if the column is part of a PRIMARY KEY. The constraint should be in an ENABLE VALIDATE state."
    BUT BY DEFAULT ALL CONSTRAINTS ARE IN VALIDATE STATE
    (Ref: Oracle® Database SQL Reference
    10g Release 2 (10.2)
    Part Number B14200-02 )Note : I use OraDB 10g v.2
    Thanks a lot
    Sim

    Hi,
    Tom Kytes answer it before:
    SQL> create table t ( id int );
    Table created.
    SQL> desc t
    Name                            Null?    Type
    ID                                       NUMBER(38)
    SQL> alter table t add constraint t_nn check (id is not null);
    Table altered.
    SQL> insert into t (id) values (null);
    insert into t (id) values (null)
    ERROR at line 1:
    ORA-02290: check constraint (TANDREWS.T_NN) violated
    SQL> desc t
    Name                            Null?    Type
    ID                                       NUMBER(38)
    Followup July 16, 2003 - 10am US/Eastern:
    that is not a NOT NULL constraint, that is a check constraint
    ops$tkyte@ORA920LAP> create table t ( x int );
    Table created.
    ops$tkyte@ORA920LAP> alter table t modify x not null;
    Table altered.
    ops$tkyte@ORA920LAP> set linesize 50
    ops$tkyte@ORA920LAP> desc t
    Name                    Null?    Type
    X                       NOT NULL NUMBER(38)To see the full thread in asktom, please refer to:
    - http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:1338402651192
    Cheers,
    Francisco Munoz Alvarez
    http://www.oraclenz.com

  • EA2: Code is generated for only one column with Domain check constraint.

    I created a Domain with a Value List (Y or N - Yes or No) and used that domain for two columns in the same table. But for only one column (the last one) the check appears in the generated DDL.
    After I enabled the "Use Domain Constraints" both checks appear in the DDL, but one as an inline check constraint and one as an "Alter table add contraint.."
    Once I changed the naming Template for the check constraint, both constraints are generated as an Alter table clause. The inline check constraint is only generated when the name of the constraint (according to the template) is too long. It would be nice if I could choose if I want an inline or a separate check constraint definition.
    Edited by: Roel on Nov 23, 2010 11:55 AM
    Edited by: Roel on Nov 23, 2010 12:02 PM

    I logged ER for that
    Philip

  • Performance Impact of Unique Constraint on a Date Column

    In a table I have a compound unique constraint which extends over 3 columns. As a part of functionality I need to add another DATE column to this unique constraint.
    I would like to know the performance implications of adding a DATE column to the unique constraint. Would the DATE column behave like another VARCHAR2 or NUMBER column, or would it degrade the performance significantly?
    Thanks
    Message was edited by:
    user627808

    What performance are you concerned about degrading? Inserts? Or queries? If you're talking about queries, what sort of access path are you concerned about?
    Are you concerned that merely changing the definition of the unique constraint would impact performance? Or are you worried that whatever functional change you are making would impact performance (i.e. if you are now retaining historical data in the table rather than just updating it)?
    Regardless of the performance impact, unique indexes (and unique constraints) need to be correct. If you need to allow duplicates on the 3 current columns with different dates, then you would need to change the unique constraint definition regardless of the performance impact. Fast and wrong generally isn't going to be preferrable to slow and right.
    Generally, though, there probably is no reason to be terribly concerned about performance here. Indexing a date is no different than indexing any other primitive data type.
    Justin

  • Problem in enabling constraint - after disabling and truncation of table .

    Hello Friends,
    I have a table called DRR_TABLES that has list of table names . The requirement is to truncate the tables present in DRR_TABLES except KEY_IDS table and table_name like '%TYPE%' table.
    written a procedure . successfullly truncating the tables from DRR_TABLES but while enabling constraints after truncation , I am getting problem in enabling constraints .
    ERROR at line 1:
    ORA-02270: no matching unique or primary key for this column-list
    ORA-06512: at "schema123.TRUNCATE_DRR_TABLES ", line 49
    ORA-06512: at line 1
    Heres is the code .
    PROCEDURE TRUNCATE_DRR_TABLES is
    x varchar2(200);
    v_tablecount number := 0;
    cursor c is select TABLE_NAME from DRR_TABLES where population_source='PUBLISHING' and TABLE_NAME != 'KEY_IDS' and TABLE_NAME NOT LIKE '%TYPE%';
    BEGIN
    DBMS_OUTPUT.PUT_LINE (' TRUNCATING DRR TABLES ...........');
    OPEN c ;
    LOOP
    FETCH c INTO x ;
    EXIT WHEN c%NOTFOUND;
    for c1 in (select table_name, constraint_name from user_constraints where TABLE_NAME = x and status ='ENABLED' ORDER BY CONSTRAINT_TYPE DESC )
    loop
    begin
    execute immediate ('alter table '||c1.table_name||' disable constraint '||c1.constraint_name|| ' cascade');
    NULL;
    end;
    end loop;
    EXECUTE IMMEDIATE 'TRUNCATE TABLE ' || x ;
    v_tablecount := v_tablecount + 1 ;
    DBMS_OUTPUT.PUT_LINE('TABLE TRUNCATED :'|| x );
    END LOOP ;
    DBMS_OUTPUT.PUT_LINE (' TOTAL TABLES TRUNCATED ' || v_tablecount );
    CLOSE c;
    OPEN c ;
    LOOP
    FETCH c INTO x ;
    EXIT WHEN c%NOTFOUND;
    for c2 in (select table_name, constraint_name from user_constraints where TABLE_NAME = x and status = 'DISABLED' ORDER BY CONSTRAINT_TYPE)
    loop
    begin
    execute immediate ('alter table '||c2.table_name||' enable constraint '||c2.constraint_name);
    NULL;
    end;
    end loop;
    END LOOP ;
    CLOSE c ;
    END TRUNCATE_DRR_TABLES ;
    LINE 49 is the line corresponding to enable constraint statement.
    Edited by: kumar73 on 3 Sep, 2012 11:44 PM

    It is such a pity that a user having 321 posts till date is unaware of basics of Posting a Question.
    1. You need to provide us with your Oracle version
    select * from v$version;2. You need to understand and get accustomed to using tags before and after Code or SQL's for better readability.
    3. You need to provide us with the Table Structure and the Constraints Definition.
    There are many things that looks like Bad Coding practices:
    <font face="Times New Roman" size=2>
    1. Avoid RBAR (Loops).
    2. Implement Bulk Collect.
    3. Why do you need to disable the constraints before truncating? Are you kind of handling the Referential Integrity Constraints?
    4. Duplicate checking of Disabled Constraints.
    5. When the procedure is being executed at Production Environment, are you going to Monitor the DBMS_OUTPUT? Why not Log the Statements into a LOG Table?
    6. Why use a TableCount variable? Would the TableCount Variable be not equal to the Number of Records returned by Cursor C?
    7. What is the need to use a NULL statement after every Execute Immediate?
    8. What is the Need to surround each execute Immediate with Begin .. End block?
    9. Where is your Exception handling Block? Forgot to write?
    </font>
    What has been your effort in finding which Constraint/Table is causing you the trouble?                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Constraints on a XMLTYPE table

    Hi,
    Has anyone been able to construct constraints on a XMLTYPE table as shown on page 5-52 of the XDB Developers
    guide.
    Whatever I try I get errors:
    create table poc_wip2 of xmltype
    element "http://www.derwent.co.uk/wpi.xsd#WPI"
    (unique(XMLDATA.WPI_TYPE.BibPt2645_T.co))
    (unique(XMLDATA.WPI_TYPE.BibPt2645_T.co))
    ERROR at line 3:
    ORA-00922: missing or invalid option
    create table poc_wip2 p of xmltype
    element "http://www.derwent.co.uk/wpi.xsd#WPI"
    (unique(extract(value(p),/WPI/BibPt@co')))
    create table poc_wip2 p of xmltype
    ERROR at line 1:
    ORA-00922: missing or invalid option
    What I would like to be able to do is to define a primary key constraint based on three attribute values. Is this possible
    using XMLTYPE?
    Thanks
    Pete

    Peter
    Remember that the attribute names generated from the Schema are case sensitive bu SQL is not. You will have to use something like XMLDATA.WPI_TYPE."BibPt2645_T"."co" in the constraint definition
    It may be easier to create the table via registerSchema and then alter the constraint onto the table..
    EG.
    alter table purchaseorder
    add constraint REFERENCE_IS_UNIQUE
    unique (xmldata."Reference")
    alter table purchaseorder
    add constraint USER_IS_VALID
    foreign key (xmldata."User") references SCOTT.emp(ename)
    create trigger VALIDATE_PURCHASEORDER
    before insert on purchaseorder
    for each row
    declare
    XMLDATA xmltype;
    begin
    XMLDATA := :new.sys_nc_rowinfo$;
    xmltype.schemavalidate(XMLDATA);
    end;
    --quit
    The reason for this is that if you want to keep a table created from a schema in_sync with the resource view you need to call
    dbms_xdbz.enableHierarchy(SCHEMA,TABLE) after creating the table..

  • Check constraint from domain missing after generation

    Hi,
    I've got the following problem with designer 10g. When I create a column and specify a specific domain, then generate the scripts for 10g (or 8i,9,...) the check constraints that is specified in the domain goes missing. The strange part is that we have about 50 domains and 49 of them work perfect but one of them just doesn't want to be generated. I've been comparing the domain to the others but I don't see any major differences that would cause the problem. Anyone know what could cause the problem or where I should (I think it is somewhere in the design & generate part) ?
    Help would be greatly appreciated.
    Grtz
    Message was edited by:
    Yves C

    Kent,
    in the DM v3.3.0.747 I have defined domains using value lists that lets you specify data values for the domain instead of define a check constraint, example Domain Name: "YesNo" and Value List -> "Y", "N".
    After adding a new column and set with the domain created, I force to apply the standard names to table with the button "Naming Rules", and the constraint created is correctly named . Notice that I need to force to apply the standard names because by default these constraints are created without name.
    Now I checked create a domain with check constraint definition for 11g (instead of using a list of values) and the behavior was the same.
    I recently upgraded to version 4.0EA2 and it works in the same way for both, so see if forcing to apply the "naming rules" solves your issue.
    Regards.
    Ariel.

  • How to find primary constraint column

    How can i get the column names of the primary keys if i know the CONSTRAINT_NAME, and CONSTRAINT_TYPE = "P" in the user constraints of the table name.
    thanx in advance
    utsab

    Hi,
    Have you tried using the table USER_CONS_COLUMNS ?
    This has information about columns in constraint definitions.
    Hope this helps.
    Sujatha.

  • Constraints on complex object table

    I use the following sql script:
    create type item as object
         id number,
         value number
    create type item_list as table of item;
    create type entry as object
         id number,
         entry_name varchar2(50),
         items item_list
    create table entries of entry
    oidindex entries_oid_idx (tablespace indx)
    nested table items store as entries_items;
    This will create two constraints (ENTRIES_OID_IDX ans SYS_C00xxx) on the table 'entries'. How can i tell the server to store both constraints (not only the oid index) to the tablespace indx?
    Thank you
    Toby

    Peter
    Remember that the attribute names generated from the Schema are case sensitive bu SQL is not. You will have to use something like XMLDATA.WPI_TYPE."BibPt2645_T"."co" in the constraint definition
    It may be easier to create the table via registerSchema and then alter the constraint onto the table..
    EG.
    alter table purchaseorder
    add constraint REFERENCE_IS_UNIQUE
    unique (xmldata."Reference")
    alter table purchaseorder
    add constraint USER_IS_VALID
    foreign key (xmldata."User") references SCOTT.emp(ename)
    create trigger VALIDATE_PURCHASEORDER
    before insert on purchaseorder
    for each row
    declare
    XMLDATA xmltype;
    begin
    XMLDATA := :new.sys_nc_rowinfo$;
    xmltype.schemavalidate(XMLDATA);
    end;
    --quit
    The reason for this is that if you want to keep a table created from a schema in_sync with the resource view you need to call
    dbms_xdbz.enableHierarchy(SCHEMA,TABLE) after creating the table..

  • SQL for views with constraints

    We use a product that requires us to have pk's on all of our views. So when I generate the SQL using DBMS_METADATA or using SQL Developer we have to keep the original scripts so that we can manually insert the constraint definition into the generated script.
    I noted that while browsing the SQL tab for each view I can see the constraint in the view definition. So where is this tab generating it's SQL from? It's not in the text of the view, and dbms_metadata does not seem to do it.
    It would be useful for me to be able to generate them with the constraint in the text already as this process that we do now is cumbersome.
    Can anyone tell me where/how I can do that?
    Cheers,
    Henri

    OK, here is little test:
    alter view emp_sal
    add constraint emp_sal_uk unique (ename) DISABLE NOVALIDATE ;
    After that command the view definition is
    CREATE OR REPLACE FORCE VIEW "SCOTT"."EMP_SAL" ("EMPNO", "ENAME", "SAL",
         UNIQUE ("EMPNO") RELY DISABLE,
         CONSTRAINT "ID_PK" PRIMARY KEY ("EMPNO") RELY DISABLE,
         CONSTRAINT "EMP_SAL_UK" UNIQUE ("ENAME") DISABLE) AS
    SELECT empno, ename, sal FROM emp;
    so that the constraint becomes effectively inline. It is displayed with
    select dbms_metadata.GET_DDL('VIEW', 'EMP_SAL') from dual;

  • Enabling Constraints

    Hi All,
    Some generic conceptual questions.
    Oracle Database Version: 11.1.0.7
    1) Is there any time difference between enabling constraint on a Non-partitioned table and enabling constraint on a partitioned table, both tables having same no. of records?
    2) Suppose, we have 3 tables A, B and C.
    B and C have FK on Table A. After loading data I want to enable constraints on table B and C. Can I do that in parallel? Or do I have to wait for one table to enable constraint and then start enabling FK constraint for the second table? Is there some locking mechanism, which enables lock on Table A while enabling FK on table B is happening?
    Thanks,
    Ishan
    Edited by: Ishan on May 12, 2012 3:54 PM

    >
    Hi,
    1) Is there any time difference between enabling constraint on a Non-partitioned table and
    enabling constraint on a partitioned table, both tables having same no. of records? http://docs.oracle.com/cd/B10501_01/server.920/a96521/partiti.htm
    =====================
    Partitions and subpartitions of a table or index all share the same logical attributes. For example, all partitions (or subpartitions) in a table share the same column and constraint definitions, and all partitions (or subpartitions) of an index share the same index options. They can, however, have different physical attributes (such as TABLESPACE).
    ======================
    2) Suppose, we have 3 tables A, B and C.
    B and C have FK on Table A. After loading data I want to enable constraints on table B and C.
    Can I do that in parallel? Or do I have to wait for one table to enable constraint and then start
    enabling FK constraint for the second table? Is there some locking mechanism, which enables
    lock on Table A while enabling FK on table B is happening?Why in parallel? AFAICS from the docco above, enabling CONSTRAINTs is a "binary" thing for all partitions - it's
    either enabled or it's not.
    Are you enabling this on a production server while updates are taking place? You might wish to consider
    looking at DEFERRABLE? But, you use the term "loading" so this isn't prod?
    Googling "enable constraint partitioned table" and "constraint deferrable oracle partitioned table" gave several
    interesting pages which may be of interest, but I don't know enough about your case to help further.
    HTH all the same,
    Paul...
    IshanEdited by: Paulie on 12-May-2012 20:42

  • How to edit a Constraint details

    The Object Browser does not allow you to review and to edit Constraints (foreign keys for example) details and to edit it except enabling/disabling and dropping.
    How can I review the details of constrains in the Object Browser?
    What SQL command should be used to query the constraints of a table.
    Thank you!
    Message was edited by:
    MarcoPolo

    Don't know how it is in object browser but in sql it looks as follows
    SQL> create table persons (
      2  prs_name varchar2(40) not null,
      3  prs_surname varchar2(40) not null,
      4  prs_age number(3),
      5  constraint prs_pk primary key (prs_name, prs_surname));
    Table created.
    SQL> create table person_addresses (
      2  pad_prs_name varchar2(40) not null,
      3  pad_prs_surname varchar2(40) not null,
      4  pad_country varchar2(40) not null,
      5  pad_city varchar2(40),
      6  pad_region varchar2(40),
      7  constraint pad_ck1 check (pad_city is not null and pad_region is null
      8                         or pad_city is null and pad_region is not null),
      9  constraint pad_prs_fk foreign key (pad_prs_name, pad_prs_surname)
    10             references persons (prs_name, prs_surname));
    Table created.
    SQL> select table_name, constraint_name, constraint_type from user_constraints
      2  where table_name in ('PERSONS', 'PERSON_ADDRESSES');
    TABLE_NAME                     CONSTRAINT_NAME                C
    PERSONS                        SYS_C0090483                   C
    PERSONS                        SYS_C0090484                   C
    PERSONS                        PRS_PK                         P
    PERSON_ADDRESSES               SYS_C0090486                   C
    PERSON_ADDRESSES               SYS_C0090487                   C
    PERSON_ADDRESSES               SYS_C0090488                   C
    PERSON_ADDRESSES               PAD_CK1                        C
    PERSON_ADDRESSES               PAD_PRS_FK                     R
    8 rows selected.
    SQL> desc user_cons_columns
    Name                                                  Null?    Type
    OWNER                                                 NOT NULL VARCHAR2(30)
    CONSTRAINT_NAME                                       NOT NULL VARCHAR2(30)
    TABLE_NAME                                            NOT NULL VARCHAR2(30)
    COLUMN_NAME                                                    VARCHAR2(4000)
    POSITION                                                       NUMBER
    SQL> select table_name, constraint_name, column_name
      2  from user_cons_columns
      3  where table_name in ('PERSONS', 'PERSON_ADDRESSES')
      4  order by table_name, constraint_name, position;
    TABLE_NAME                     CONSTRAINT_NAME
    COLUMN_NAME
    PERSON_ADDRESSES               PAD_CK1
    PAD_CITY
    PERSON_ADDRESSES               PAD_CK1
    PAD_REGION
    PERSON_ADDRESSES               PAD_PRS_FK
    PAD_PRS_NAME
    PERSON_ADDRESSES               PAD_PRS_FK
    PAD_PRS_SURNAME
    PERSON_ADDRESSES               SYS_C0090486
    PAD_PRS_NAME
    PERSON_ADDRESSES               SYS_C0090487
    PAD_PRS_SURNAME
    PERSON_ADDRESSES               SYS_C0090488
    PAD_COUNTRY
    PERSONS                        PRS_PK
    PRS_NAME
    PERSONS                        PRS_PK
    PRS_SURNAME
    PERSONS                        SYS_C0090483
    PRS_NAME
    PERSONS                        SYS_C0090484
    PRS_SURNAME
    11 rows selected.And you can always get info about data dictionary either from dictionary itself or reference manual.
    SQL> select * from dict where table_name like '%CONS%';
    TABLE_NAME
    COMMENTS
    USER_CONSTRAINTS
    Constraint definitions on user's own tables
    <other rows skipped>Gints Plivna
    http://www.gplivna.eu
    P.S. I'm absolutely not advising to create tables with such stupid structure :)

  • Log error while loading a war file to WAs

    When trying to load a war file to WAs and selecting the class loader option "Parent last", I get an error:
    Caused by: org.apache.commons.logging.LogConfigurationException: The chosen LogFactory implementation does not extend LogFactory. Please check your configuration. (Caused by java.lang.ClassCastException: The application has specified that a custom LogFactory implementation should be used but Class 'com.ibm.ws.commons.logging.TrLogFactory' cannot be converted to 'org.apache.commons.logging.LogFactory'.
    I read the mailing list and solution suggested is
    replace the commons-logging-api.jar with commons-logging-adapters.jar,i did that doing this i get the error
    Class org/xml/sax/DTDHandler violates loader constraints: definition mismatch between parent and child loaders
    Can someone suggest what should i do?

    Hi,
    Are you creating a table and loading it in Openscript??
    If so, can you show the screen shot.
    One more information , you can also change the Excel sheet into a CSV file and you can add it as a databank in the Tree view of the Openscript.
    Thanks and Regards,
    Nishanth Soundararajan.

  • Error while saving Employee Billrates through OAF page

    Dear All,
    I am facing the below mentioned error while saving Employee Bill rates for any project through OAF interface. I have tried saving the same through FORMS interface and its getting saved. The Unique constraint on the error log is on the table PA_EMP_BILL_RATE_OVERRIDES and the column is EMP_BILL_RATE_OVERRIDE_ID and we have a sequence for generating Unique id. The sequence used is PA_EMP_BILL_RATE_OVERRIDES_S.
    Please note that the error only fires on insertion of new record in the table PA_EMP_BILL_RATE_OVERRIDES, on updation error doesn't fire.
    The Constraint definition on the table is :
    create unique index PA.PA_EMP_BILL_RATE_OVERRIDES_U2 on PA.PA_EMP_BILL_RATE_OVERRIDES (EMP_BILL_RATE_OVERRIDE_ID)
    ERROR : java.sql.SQLException: ORA-00001: unique constraint (PA.PA_EMP_BILL_RATE_OVERRIDES_U2) violated

    Dear All,
    I am facing the below mentioned error while saving Employee Bill rates for any project through OAF interface. I have tried saving the same through FORMS interface and its getting saved. The Unique constraint on the error log is on the table PA_EMP_BILL_RATE_OVERRIDES and the column is EMP_BILL_RATE_OVERRIDE_ID and we have a sequence for generating Unique id. The sequence used is PA_EMP_BILL_RATE_OVERRIDES_S.
    Please note that the error only fires on insertion of new record in the table PA_EMP_BILL_RATE_OVERRIDES, on updation error doesn't fire.
    The Constraint definition on the table is :
    create unique index PA.PA_EMP_BILL_RATE_OVERRIDES_U2 on PA.PA_EMP_BILL_RATE_OVERRIDES (EMP_BILL_RATE_OVERRIDE_ID)
    ERROR : java.sql.SQLException: ORA-00001: unique constraint (PA.PA_EMP_BILL_RATE_OVERRIDES_U2) violated

Maybe you are looking for