Results 1 to 3 of 3
  1. #1
    Join Date
    Jan 2003
    Location
    Bangalore
    Posts
    36

    Unanswered: Deciphering actual cause of error from "SQL0803N" Error message

    While inserting duplicate records in a non-primary Unique key field, I am getting errors like this.

    SQL0803N One or more values in the INSERT statement, UPDATE
    statement, or foreign key update caused by a DELETE statement
    are not valid because the primary key, unique constraint or
    unique index identified by "2" constrains table
    "ADMINISTRATOR.TEMP_CARRIER
    " from having duplicate rows for those columns.

    Now my question is, how can I differentiate the actual cause of the error,
    i.e., whether the error is because of a duplicate primary key or is it because of duplicate non-primary unique keys.

    From the above error message there is no separate indication for primary key or unique key.


    Is there any way to solve this problem?

  2. #2
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: Deciphering actual cause of error from "SQL0803N" Error message

    I'm not very sure , but see if the statement event monitor helps you .

    Cheers

    Sathyaram


    Originally posted by sandips
    While inserting duplicate records in a non-primary Unique key field, I am getting errors like this.

    SQL0803N One or more values in the INSERT statement, UPDATE
    statement, or foreign key update caused by a DELETE statement
    are not valid because the primary key, unique constraint or
    unique index identified by "2" constrains table
    "ADMINISTRATOR.TEMP_CARRIER
    " from having duplicate rows for those columns.

    Now my question is, how can I differentiate the actual cause of the error,
    i.e., whether the error is because of a duplicate primary key or is it because of duplicate non-primary unique keys.

    From the above error message there is no separate indication for primary key or unique key.


    Is there any way to solve this problem?

  3. #3
    Join Date
    Jan 2003
    Location
    Bangalore
    Posts
    36
    I have to decipher the error message from inside an EJB bean, so event monitor would not really help.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •