Re: ORA-00600: internal error code

ORA-600 [729] is a space leak in the UGA. There are patchsets available which can fix your problem. You should be at 8.1.7.4 or 9.2.0.3. If that is not possible, add the following to your INIT.ORA and bounce your instance:

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

The level (4000 in the case above) tells the system not to put ORA-600 error messages in your Alert Log until the space leak is over that number of bytes. In your case, the space leak was 80 bytes so a level of 4000 won't produce this error message.

HTH,
Brian

mkoster wrote:
>
> hi,
>
> aix 4.3.3 on rs6000;
> oracle 8.1.7.0.0
>
> every day i get even more error-messages in the alert.log
>
> Errors in file
> /dba/app/oracle/product/817/admin/NTEL/udump/ora_102634_ntel.trc:
> ORA-00600: internal error code, arguments: [729], [80], [space leak],
> [], [], [], [], [].
>
> in the user-log i get:
> >>>>>
> *** 2003-07-23 15:41:51.811
> *** SESSION ID:(531.7526) 2003-07-23 15:41:51.809
> ******** ERROR: UGA memory leak detected 80 ********
> ******************************************************
> HEAP DUMP heap name="session heap" desc=0x1101de478
> extent sz=0x10a8 alt=32767 het=32767 rec=0 flg=3 opc=3
> parent=11000d2f0 owner=700000000648ef8 nex=0 xsz=0x10a8
> EXTENT 0
> Chunk 1103a09a0 sz= 4248 free " "
> EXTENT 1
> ......
> <<<<<
>
> what can i do ???
>
> thanks marcus
>
> --
> Posted via http://dbforums.com

-- 
===================================================================

Brian Peasland
dba_at_remove_spam.peasland.com

Remove the "remove_spam." from the email address to email me.


"I can give it to you cheap, quick, and good. Now pick two out of
 the three"