ORA-00001: unique constraint (UNKNOWN.obj#=179690) violated [message #632737] |
Thu, 05 February 2015 03:02 |
famegaurav
Messages: 23 Registered: November 2010 Location: Delhi India
|
Junior Member |
|
|
In our application logs we got the below oracle error not mentioning the constraint name during one of the insert process.
ORA-00001: unique constraint (UNKNOWN.obj#=179690) violated
Request you to please help me to identify the possible reason for that
|
|
|
|
|
|
Re: ORA-00001: unique constraint (UNKNOWN.obj#=179690) violated [message #632744 is a reply to message #632741] |
Thu, 05 February 2015 03:25 |
famegaurav
Messages: 23 Registered: November 2010 Location: Delhi India
|
Junior Member |
|
|
Yes this query will give the object name and based on object name we can findout the constraint name also , but my question is why application logs write oracle error error in this format , is something wrong at oracle end or Java is misinterpretation oracle at any point or not able to find out the contraint name
|
|
|
|
|
Re: ORA-00001: unique constraint (UNKNOWN.obj#=179690) violated [message #648485 is a reply to message #632746] |
Wed, 24 February 2016 01:00 |
|
Michel Cadot
Messages: 68641 Registered: March 2007 Location: Nanterre, France, http://...
|
Senior Member Account Moderator |
|
|
Quote:I don't think any of us have seen this behaviour before
I did.
This happens when vendor sells with his product (or makes at custom site) the database without executing CATALOG.SQL script, something that is optional, Oracle does not need the catalog views to work.
What is surprising is when OP says: "Yes this query will give the object name" as this is not possible in his database.
[Updated on: Wed, 24 February 2016 01:02] Report message to a moderator
|
|
|