Hi there,
I would like to simulate ORA-03114 in a test application and I would like to get some clues as to how to do this.

Since people are probably going to ask why I want to do that, here is some background. An Oracle client application of ours that
connects to Oracle via OCI, sometimes faces loss of connection, for example when a lap to goes into hibernation or the network is
unstable. We are speaking of a Windows 2000, XP, Vista client here. Now we want to improve the error handling in our application in
this specific case. That is no problem because ORA-03114 can be detected and appropriate measures can be taken (error message,
automatic reconnection, ...).

However for every issue that we fix in our applications we are writing a test case which will test a particular behaviour or bug
fix. We do this in form of unit tests, so the unit test application will simply run for a short or long span of time without user
interaction and protocol what happened, for example how many of the tests succeeded and how many failed.

The loss of connection we dont know how to simulate. One way is to use OEM and manually KILL the session at the appropriate point
of time and see what the application will do. But that requires user interaction, so its not like you can run the tests over night
and just scan the protocol the next morning...

We are using MS Dev studio 2005/2003 and the standard OCI library. Thanks very much in advance

André

André Hartmann wrote:
Some Oracle error messages for example, ORA-03114 not connected to
ORACLE, are not root causes but rather the result of something else.
A session might be disconnected for hundreds of reasons.

Trapping for a lack of connection will tell you nothing about why or
how you got there. For that you need to use:
DBMS.UTILITY.FORMAT_ERROR_BACKTRACE
DBMS.UTILITY.FORMAT_CALL_STACK
DBMS.UTILITY.FORMAT_ERROR_STACK

Demos in Morgan's Library at www.psoug.org under DBMS_UTILITY.

If all you want to do is create a disconnection pull the CAT5 cable
out of the back of a machine or use ALTER SYSTEM KILL SESSION:
Demostrated in the Library under KILLING SESSIONS.
--
Daniel A. Morgan
Oracle Ace Director & Instructor
University of Washington
damorgan@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org

"DA Morgan" <damorgan (AT) psoug (DOT) org> schrieb im Newsbeitrag news:1194616637.115847 (AT) bubbleator (DOT) drizzle.com...

Yes, I know that. I am not aiming at tracking down the reason here, I am aiming at testing the application code, that reacts to the
occurrence of the event. For example the reaction could be to establish a new connection to the schema and continue as normal.

On Fri, 9 Nov 2007 14:19:51 +0100, André Hartmann
<andre.hartmann (AT) hotmail (DOT) de> wrote:

According to the documentation:

ORA-03114 not connected to ORACLE

Cause: A call to Oracle was attempted when no connection was
established. Usually this happens because a user-written program has
not logged on. It may happen if communication trouble causes a
disconnection. In addition, this message could occur when ALTER SYSTEM
KILL SESSION or ALTER SYSTEM DISCONNECT SESSION were issued with the
IMMEDIATE qualifier because, in those cases, the client's connection
to the database is terminated without waiting for the client to issue
a request.

Action: Try again. If the message recurs and the program is user
written, check the program.

B.

André Hartmann wrote:
But the application code is meaningless for this error message. Is the
cause of the disconnect that the Oracle client had a brain hemmorhage?
Or that the CAT5 cable is disconnected? Or the fact that someone on the
server did SHUTDOWN ABORT? You don't know. You can not know. And there
is nothing your application can do about it except keep trying to
reconnect for some finite period before timing out.
--
Daniel A. Morgan
Oracle Ace Director & Instructor
University of Washington
damorgan@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org

"André Hartmann" <andre.hartmann (AT) hotmail (DOT) de> wrote

Raise application error , kill

André Hartmann wrote:

Not familiar with these, but in SQL*Plus, you can issue
a "disconnect". It's the (seldom used) counterpart of
"connect <user>[/password][@tns_alias]"

--
Regards,
Frank van Bortel

Top-posting is one way to shut me up...

On Fri, 9 Nov 2007 12:45:34 -0500, "Paul" <paulq_1998 (AT) yahoo (DOT) com>
wrote:

You cannot raise that error.

B.

Brian Tkatch wrote:

Actually you can using ORADEBUG but you would need to get Oracle support
to tell how.
--
Daniel A. Morgan
Oracle Ace Director & Instructor
University of Washington
damorgan@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org

On Fri, 09 Nov 2007 11:49:21 -0800, DA Morgan <damorgan (AT) psoug (DOT) org>
wrote:

Interesting.

B.