Re: Wait event SQL*Net break/reset to client caused by duplicate insert?
- From: "Peter Hitchman" <pjhoraclel@xxxxxxxxx>
- To: "Tanel Poder" <tanel.poder.003@xxxxxxx>
- Date: Thu, 10 Apr 2008 10:19:29 +0100
Hi Tanel,
Thanks for the feedback. Talking to the developer about the code, I
suggested a change to first update and then insert if no row is updated. I
also considered using merge, but I thought that it might not be supported by
the jdbc driver and time pressure means we do not have the time to find out.
Regards
Pete
On Wed, Apr 9, 2008 at 5:53 PM, Tanel Poder <tanel.poder.003@xxxxxxx> wrote:
> 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
>
>
> ------------------------------
> *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).
>
>
>
--
Regards
Pete
Other related posts:
