Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: FRANTIC! ORA-03113 Acessing Specific, Random Tables
Thanks! I found the core.log file and it has numerous entries that
coincide with the client error times. The entry always starts with:
Oracle8i Release 8.1.7.1.1 - Production
Process Id: 0s000003b4 Thread Id : 0x000008ec Time: Tue Sep 03
12:31:19
Excp. Code: 0xc0000005 Excp. Type: ACCESS_VIO Flags: 0x00000000
or something similar. I'll try to dissect it and see what it tells me. And in order to clarify, it is only one table at a time, usually several days apart. That's part of the reason I don't really see it as a network issue. It's always very consistent in that everything works fine until you try to change data in the table in question and then you immediately get bumped. I thought that if it were a network problem it would be more random or affect more than one table. Out of millions of packets, I'm only seeing less than a dozen errors on the nic, switches and routers. Am I not looking at something I should? Thanks again for all your help.
"Niall Litchfield" <niall.litchfield_at_dial.pipex.com> wrote in message news:<3d75db0e$0$8509$cc9e4d1f_at_news.dial.pipex.com>...
> 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
> ******************************************
Received on Wed Sep 04 2002 - 11:35:44 CDT