Re: FRANTIC! ORA-03113 Acessing Specific, Random Tables

"Niall Litchfield" <niall.litchfield_at_dial.pipex.com> wrote in message news:<3d75db0e$0$8509$cc9e4d1f_at_news.dial.pipex.com>...
> "Arielle Smith" <smithari_at_hotmail.com> wrote in message
> news:677227cc.0209032104.6c0b4b19_at_posting.google.com...
> > We are getting ORA-03113 errors when trying to change data in specific
> > tables in our Oracle DB and it is never the same table twice. We have
> > an application front end that throws an "Oracle connection lost" error
> > when the user tries to perform certain actions.

<<SNIP>>

> I'd second Billy's suggestion to recheck this We had an Ora-03113 recently
> that was down to poor network drivers. The network connection functioned
> just fine apparently, but packet sniffing revealed almost 10% of TCP/IP
> packets were timing out. Changed the (somewhat exotic) network card
> configuration and updated the drivers and the problem went away.
>
> In addition as Vladimir says if a process has died on the server side there
> will be a trace file in the background dump destination on the server. IIRC
> they are named CORE***.log
>
>
> > *****Used the client software tracing function (this is where I
> > discovered the ora-03113 entry:
> > 717393562> SQL HostVar: :hvDEANUMBER =
> > 717393562> SQL HostVar: :hvLICNUMBER = (this was the last value in the
> > insert stmt)
> > 717393859> ERROR: 32786 COULDN'T FIND THE SYMBOL: _MLErrFile (this is
> > specific to the app)
> > 717393906> ORA-03113: end-of-file on communication channel
> > 717393906> ERROR: 32802 ORA-03113: end-of-file on communication
> > channel
> > ORA-03113: end-of-file on communication channel
>
> Obviously I don't know the app but having one error in a trace file
> *immediately* before another usually means the first error is the cause. So
> check this out with the vendor
>
> If you can establish that it really isn't the app and none of our stabs in
> the dark work out then you should be raising a TAR with Oracle (who may well
> ask you to patch to 8.1.7.4)
>
>
> --
> Niall Litchfield
> Oracle DBA
> Audit Commission UK
> *****************************************
> Please include version and platform
> and SQL where applicable
> It makes life easier and increases the
> likelihood of a good answer
> ******************************************

Just as a follow up, thanks for all the wonderful help. I've now identified that the core dumps are a result of missing triggers (now a separate post). After the triggers disappear, so results the core dumps. Did I say my brain hurts at this point? Thanks again for your patience and effort. Received on Mon Sep 09 2002 - 16:51:24 CDT