SQL*Net break/reset to client  There was a question in Oracle-L
mailinglist recently, regarding excessive SQL*Net break/reset to
client waiting by a session.  A quote is below:  We are seeing
an insert statement reporting “SQL*Net break/reset to client” as
over 1/3 of its time. On the face of it this event suggests
network issues but nothing else backs this up as the cause. So I
looked at the Java code in question and a trace of one of the
sessions. What is happening is that an attempt is made to insert
a row, most of the time a duplicate error results, the code
catches this exception and does an update. I was wondering if
its the duplicate error and the exception handling which results
in this wait event showing up.  My answer to that was following:
Yes, a SQL*Net break/reset happens when an error/unhandled
exception is raised during a call (which means that the call
executed didn’t complete normally, thus the call state must be
reset).  The approach of “insert -> if failed then update” is
basically what ME