ORA-00600 [723], [67108952], [pga heap] When Event 10261 Set To Limit The PGA Leak (Doc ID 1162423.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.4 to 10.2.0.5 [Release 10.2]
Information in this document applies to any platform.
***Checked for relevance on 23-Nov-2012***

Symptoms


ORA-00600: internal error code, arguments: [723], [67108952], [pga heap], [], [], [], [], []



In trace file....

ERROR: PGA size limit exceeded: 3224886936 > 3221225472
--------------------------------------------------------------------------------------
HEAP DUMP heap name="pga heap" desc=0x685f220
extent sz=0x20c0 alt=184 het=32767 rec=0 flg=2 opc=1
parent=(nil) owner=(nil) nex=(nil) xsz=0x400fff0
EXTENT 0 addr=0x2b50136010
Chunk 2b50136020 sz= 65432 free " "
Chunk 2b50145fb8 sz= 67108936 freeable "qesmmCheckPgaL " ds=0x2a97c2b1e8
EXTENT 1 addr=0x2b4c126010

 

Call stack functions
---------------------------------

ksmapg <- kghgex <- kghfnd <- kghalo<- kghgex <- kghfnd <- kghprmalo <- kghalp <- qesmmCheckPgaLimit

 

Changes

#In init.ora/spfile.ora, the below event have been set to limit the PGA memory leak.

 
Event 10261 "Limit the size of the PGA heap

Event 10261
Text: Limit the size of the PGA heap

Description:
This event is useful for PGA memory leaks (and UGA if the UGA is in the PGA). The event causes Oracle to raise an ORA-600 if the PGA tries to grow above the specified size. A PGA heapdump is produced but additional information can be dumped for other heaps by setting an event on ORA-600 within the target process.

Level:
The limit is one kilobyte times the level of the event. If the pga grows bigger than this we signal an internal error.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms