RE: Wait event SQL*Net break/reset to client caused by duplicate insert?

From: Tanel Poder <tanel.poder.003@xxxxxxx>
To: pjhoraclel@xxxxxxxxx, "'oracle-l'" <oracle-l@xxxxxxxxxxxxx>
Date: Thu, 10 Apr 2008 00:53:31 +0800

FYI, I did put together a small test case with further explanation to my
blog:
 
http://blog.tanelpoder.com/2008/04/10/sqlnet-breakreset-to-client/

--
Regards,
Tanel Poder
http://blog.tanelpoder.com <http://blog.tanelpoder.com/> 


 



  _____  

From: Tanel Poder [mailto:tanel.poder.003@xxxxxxx] 
Sent: Thursday, April 10, 2008 00:05
To: 'pjhoraclel@xxxxxxxxx'; 'oracle-l'
Subject: RE: Wait event SQL*Net break/reset to client caused by duplicate
insert?


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).

Follow-Ups:

Re: Wait event SQL*Net break/reset to client caused by duplicate insert?
From: Peter Hitchman

References:
- Wait event SQL*Net break/reset to client caused by duplicate insert?
  - From: Peter Hitchman

RE: Wait event SQL*Net break/reset to client caused by duplicate insert?

Other related posts: