Hi All,

For about a week and a half I have been trying to solve a mysterious
issue with unique constraint violations on our database server without
any luck.

We basically have a simple table with a unique primary key (number) and
a few string columns that aren't part of the key.

With J2EE on the Sun App Server 7, we always make sure we get the
nextval from the table's sequence before inserting it into the table. I
have checked this numerous times.

The Oracle DB doesn't have any triggers or other procedures accessing
the table in any way.


Has anybody heard of this issue or know how to fix it?

Regards,

Nikk

Have you tried tracing the sessions ? How many concurrent sessions is
your applications generating ?
ndamianov wrote:

Renzo Zagni wrote:
How are you generating the nextval? Are your app users trying to
re-submit values that they aren't sure have been entered due to page
errors, etc?

More info would be helpful.

Roger

ndamianov wrote:
Go to www.psoug.org and click on Morgan's Library
Scroll down to DBMS_ERRLOG.

Implement a log and when errors occur next ... trace them
back to the value in the sequence.

BTW: When you write "the table's sequence" ... tables don't have
sequences. A sequence is completely independent of any table or
tables. Be sure something else isn't using the same sequence.
--
Daniel A. Morgan
University of Washington
damorgan@x.washington.edu
(replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org