Re: core dump problem!!!!

Hi,

this is bug 438057, and is described in note 1058713.6 (viewable on metalink).
However, there is still no fix, as no reproducible case has been found (this is despite it being around since Oracle 7 days).

I am having the same problem also, but on solaris 2.6

The only suggested fix is to include the following event in the init.ora

event="10691 trace name context forever, level 1"

if that fails, increase to level 2

HTH NeilC

ddf_dba_at_my-deja.com wrote:
>
> In article <01bf9d9f$b2a6cce0$1264a3ca_at_default>,
> "Ali Bukhari" <smab_at_cyber.net.pk> wrote:
> > Hi,
> > I have AIX 4.2.1 and Oracle 7.3.4
> > The problem is that i found many core_XXX directories in my oracle
 home
> > directory.
> > I checked the core dump destination defined in initora and wven in
> > v$parameter while my database is running. This destination is not
 same as
> > my Oracle home directory.
> >
> > Pls reply me if someone know the reason. and also tell me that how
 can i
> > find out the reason of these core dump files.
> >
> > regards,
> > Muhammad Ali Bukhari
> > ICI Pakistan.
> >
> >
>
> Muhammad,
>
> I cannot tell you the reason for finding core_XXX directories in
> $ORACLE_HOME, outside of an application writing them there, so I won't
> even try to answer that part of your post. You can find the reason for
> the core dump files with a debugger like dbx, adb or gdb. The debugger
> will load the core file and report on the reason for the core dump.
> Most likely you'll find the reason as a segmentation fault which is, I
> believe, a memory error. A likely candidate for this is an application
> error when accessing the database instance. Run the core files through
> a debugging program and see what comes out. Also, check your alert.log
> for errors that could dump core, like ORA-0600 errors. This should
> tell you the time when the errors occurred and possibly why the core
> file was created.
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Wed Apr 05 2000 - 00:00:00 CDT