Striving for Optimal Performance
  • Blog
    • Archive
    • Categories
    • Search
  • Troubleshooting Oracle Performance
    • Description
    • Structure
    • Table of Contents
    • Forewords
    • Reviews
    • Downloadable Files
    • Addenda and Errata
    • First Edition
  • Public Appearances
    • Past Public Appearances
  • Contact
  • About

ORA-00001: unique constraint (METALINK.SYS_C005417) violated

25 July 2009 3 Comments Written by Christian Antognini

ORA-00001: unique constraint (METALINK.SYS_C005417) violated

This is a partial screenshot of an application without a decent error handling.

Do you recognize it?

It goes without saying that no further comments are needed…

Uncategorized
Impact of Direct Reads on Delayed Block Cleanouts
A-Rows and DML Statements

3 Comments

  1. Gary Gary
    26 July 2009    

    Forget the application, they should be giving their unique constraints some sort of reasonable name.

    Reply
  2. Christian Antognini Christian Antognini
    26 July 2009    

    Hi Gary

    I fully agree with you about the name of unique constraints. But, IMHO, the name of the constraints is much less important than the error handling…

    Cheers,
    Chris

    Reply
  3. Mette Mette
    30 July 2009    

    Grin … maybe they are having trouble FINDING the code produing the error – if the developers are not allowed access
    to prodcution environment definitions, it can be rather tedious to find a constraint with quite another
    name in test & dev environments. I HATE unnamed constraints …..

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.