Raj,
This reminds me of a similar situation I encountered several years
ago, perhaps there will be something in it that will help...
A 3rd party app was periodically committing only 2 of 3 changes that
were required. The most likely explanation of the problem was that there was
an unhandled exception and the app was issuing a commit regardless. This
turned out to be the case. This also would explain your situation where the
app fails, but the same command run manually works.
If the debug mode of the app failed to reveal any new info, I was
going to turn on events to dump out an error stack in case of an error on
inserts. We put together a list of probable errors on an insert (privs, bad
data, unable to extend, etc.) and could have placed these events in the
init.ora. The syntax is "event = <error> trace name errorstack level 3"
where error is the error number (1555 for Snapshot too old).
Dan
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Fink, Dan
INET: [EMAIL PROTECTED]
Fat City Network Services -- 858-538-5051 http://www.fatcity.com
San Diego, California -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
