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

From: Tanel Poder <tanel.poder.003_at_mail.ee>
Date: Fri, 11 Apr 2008 00:25:53 +0800
Message-id: <013301c89b27$8c16e680$3201a8c0@windows01>

Yep, the reset happens when the exception is propagated back to client - as the client is not under Oracle server process'es control and state anymore.

--

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

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Peter Hitchman
Sent: Thursday, April 10, 2008 17:29
To: Tanel Poder
Cc: oracle-l
Subject: Re: Wait event SQL*Net break/reset to client caused by duplicate insert?

Hi,
Just to follow up, having read your Blog entry ...

The java code is handling the exception, so is there a difference in the way this event gets fired between a java JDBC programme and server side PL/SQL code, because of the client/server nature of the java?

Thanks

Pete

--

http://www.freelists.org/webpage/oracle-l Received on Thu Apr 10 2008 - 11:25:53 CDT

This message: [ Message body ]
Next message: Tanel Poder: "RE: Moving DR site from 30miles to 1600miles"
Previous message: Best, David: "RE: Scheduled Maintenance Windows & Database Change Management"
In reply to: Peter Hitchman: "Re: Wait event SQL*Net break/reset to client caused by duplicate insert?"
Next in thread: Nigel Thomas: "Re: Wait event SQL*Net break/reset to client caused by duplicate insert?"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message