Home » SQL & PL/SQL » SQL & PL/SQL » ORA-00001: unique constraint (UNKNOWN.obj#=179690) violated (Oracle11G EE)
ORA-00001: unique constraint (UNKNOWN.obj#=179690) violated [message #632737] Thu, 05 February 2015 03:02 Go to next message
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 #632738 is a reply to message #632737] Thu, 05 February 2015 03:07 Go to previous messageGo to next message
Littlefoot
Messages: 21807
Registered: June 2005
Location: Croatia, Europe
Senior Member
Account Moderator
Who creates your application logs? I presume it is you. So, check how you do that and include any additional information you need.
Re: ORA-00001: unique constraint (UNKNOWN.obj#=179690) violated [message #632740 is a reply to message #632738] Thu, 05 February 2015 03:16 Go to previous messageGo to next message
famegaurav
Messages: 23
Registered: November 2010
Location: Delhi India
Junior Member
Logs is system generated and application is designed by the vendor so i really don't know , first time i saw a ORA-00001 in this type of behavior.
Re: ORA-00001: unique constraint (UNKNOWN.obj#=179690) violated [message #632741 is a reply to message #632740] Thu, 05 February 2015 03:19 Go to previous messageGo to next message
Littlefoot
Messages: 21807
Registered: June 2005
Location: Croatia, Europe
Senior Member
Account Moderator
See whether
select *
from user_objects
where object_id = 179690

returns anything useful (I expect it to return unique constraint's name).
Re: ORA-00001: unique constraint (UNKNOWN.obj#=179690) violated [message #632744 is a reply to message #632741] Thu, 05 February 2015 03:25 Go to previous messageGo to next message
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 #632745 is a reply to message #632741] Thu, 05 February 2015 03:25 Go to previous messageGo to next message
cookiemonster
Messages: 13920
Registered: September 2008
Location: Rainy Manchester
Senior Member
I'd query all_objects rather than user_objects
Re: ORA-00001: unique constraint (UNKNOWN.obj#=179690) violated [message #632746 is a reply to message #632744] Thu, 05 February 2015 03:28 Go to previous messageGo to next message
cookiemonster
Messages: 13920
Registered: September 2008
Location: Rainy Manchester
Senior Member
I don't think any of us have seen this behaviour before, so without more information on the objects/code that's causing the error you're probably not going to get an answer. If the code is supplied by another company you should probably try asking them.
Re: ORA-00001: unique constraint (UNKNOWN.obj#=179690) violated [message #648485 is a reply to message #632746] Wed, 24 February 2016 01:00 Go to previous message
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

Previous Topic: Ref cursor ?
Next Topic: Re: Return ColumnNames in lowercase. (split from highjacked thread http://www.orafaq.com/forum/t/175479/0/unread/#msg_648450 by bb)
Goto Forum:
  


Current Time: Thu Apr 18 23:43:40 CDT 2024