Re: ORA-600 and memory space leak

> 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?
>
>

Paul,

  I just tried

     event="10262 trace name context forever,level 2000"

  and Oracle came up without any error. ('level2000' is changed to   'level 2000').

  We are running Ver 7.1.3 on NCR Unix SVR4 with TOPEND using XA interface to   talk to Oracle. A memory leak is a regular affair whenever the DB is   shutdown with existing connections (either shutdown immediate or killing the   sessions and then shutdown normal). May I know if you are also getting the   memory leak in the same situations ? Also, if you are setting the above   event, can you please tell if it helps you ?

  Thanks,
  Rukmani.
  (mani_at_tc4hq.cmc.stph.net) Received on Sun Dec 24 1995 - 03:18:35 CST