3113's are usually sign of unexpected shadow process death.
Such events are usually followed by a message in alert log
and a trace file with more detailed description of the cause.
As Mr. Morgan noted, on *ix systems this is often the result
of improper OS kernel configuration, but 3113 may also
indicate that you have hit some bug in Oracle - trace file can
tell you more (and of course it will be useful when contacting
OSS.)
And indeed, Oracle version (incl. patch level), platform name
and OS version are almost mandatory when posting questions
like this.
--
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.
"Simon" <ssdimuan_at_hotmail.com> wrote in message
news:11cdd11.0212240754.54fc81c6_at_posting.google.com...
> Hi,
>
> I'm developing a PL/SQL program that for some reason has started to
> cause ORA-03113 errors all the time - what I mean is, I execute the
> stored procedure from the SQL*Plus prompt, and it starts running, but
> - it never finishes. After a couple minutes, it stops, and I have the
> ORA-03113 error - as if something in my code actually "broke" the
> database connection. Most strange. So I'm just wondering if any of
> you experienced Oracle ninjas out there are aware of some common
> mistakes that can cause such an error, because I'm having a hard time
> figuring it out from looking at my code. I think I know what
> procedure it's in when the error occurs, but I can't really tell what
> line is doing it. Any insight or help would be greatly appreciated.
>
> Simon Dimuantes
Received on Wed Dec 25 2002 - 05:17:13 CST
