Re: ORA-600 and memory space leak

It seems to be working for us, as after setting the event, we did not get any Memory leak problems while shutting down the DB after killing active sessions.

Hope it goes smooth here after....

Thanks,
Rukmani.

>
> Thanks for your reply.
>
> I never noticed it before but perhaps you're right. It may be happening when
> other sessions are still connected to the database.
>
> What we are doing is creating a script to kill any existing sessions other
> than system or sys, then executing the script prior to issuing the shutdown
> immediate. I don't know if any sessions were active or not.
>
> But now that I have the proper format for the event parameter and have
> placed it in the init.ora file the problem won't reoccur. Right?
>
> Thanks again.
>
> >
> > > 2- the 2nd way is : To have the following line in ur init.ora
> > >
> > > event="10262 trace name context forever,level2000"
> > >
> > > This will ignore the space leaks of less than 2000 bytes .If u have leak
> > > more than 2000 bytes , it is better to call oracle again !!!
> > >
> > > I show you the contents of the trace file:
> >
> > >
> > >
> > > error 2194 detected in background process
> > > OPIRIP: Uncaught error 447. Error stack:
> > > ORA-00447: fatal error in background process
> > > ORA-02194: event specification syntax error 230 (minor error 214) near
> > 'LEVEL200
> > > 0'
> > >
> > > ORA-2194 indicates a "syntax error" within the event statement.
> > >
> > > Does anyone know the proper syntax for that statement?
> > >
Received on Sun Jan 07 1996 - 15:35:31 CST