3113 is also signaled when shadow process dies unexpectedly (core dumps).
In this case, you need to inspect generated trace files and act accordingly.
In my experience, this was almost always the case rather than transient
network errors or driver bugs.
--
Vladimir Zakharychev (bob@dpsp-yes.com) http://www.dpsp-yes.com
Dynamic PSP(tm) - the first true RAD toolkit for Oracle-based internet applications.
All opinions are mine and do not necessarily go in line with those of my employer.
"Billy Verreynne" <vslabs_at_onwe.co.za> wrote in message news:al49as$pl1$1_at_ctb-nnrp2.saix.net...
> Okay, so what does ORA-03113 actually mean? It means that for some reason,
> the TCP/IP connection between the client process and the shadow process on
> the server, has been closed. AFAIK, this only happens when either the FIN
> bit is set in the TCP packet, or when the protocol stack "decides" to
> terminate the connection for whatever reason.
>
> Duplicate IP addresses on your network for example. A badly configured
> router or gateway. A network that does not conform to ethernet rules (are
> you running cascading hubs?).
>
> I've also seen ORA-03113's due to buggy protocol stacks. Buggy network
> drivers.
>
> I would start looking at the physical network first - this is afterall what
> the ORA-03113 error complains about. Before I go and look at the SQL's that
> are being run and the tables that are being accessed.
Received on Wed Sep 04 2002 - 04:02:15 CDT
