PGA Memory Leak - ORA-00600: internal error code, arguments: [723], [120248], [245704], [memory leak]

PGA Memory Leak - ORA-00600: internal error code, arguments: [723], [120248], [245704], [memory leak]


ORA-00600: internal error code, arguments: [723], [120248], [245704], [memory leak], [], [], [], [], [], [], [], []

========= Dump for incident 103210 (ORA 600 [723]) ========
----- Beginning of Customized Incident Dump(s) -----
******** ERROR: PGA memory leak detected 245704 > 120248 ********
******************************************************
HEAP DUMP heap name="pga heap"  desc=0xb7e8bc0
 extent sz=0x20c0 alt=216 het=32767 rec=0 flg=3 opc=3
 parent=(nil) owner=(nil) nex=(nil) xsz=0xfff0 heap=(nil)
 fl2=0x60, nex=(nil), dsxvers=1, dsxflg=0x0
 dsx first ext=0x80642720
EXTENT 0 addr=0x2b2f807fd010
  Chunk     2b2f807fd020 sz=    25984    perm      "perm           "  alo=4424
  Chunk     2b2f808035a0 sz=    10680    free      "               "
  Chunk     2b2f80805f58 sz=      128    freeable  "kzam_osx_cleanu"
  ...............
  
  ----- Call Stack Trace -----
  kgdsdstsg <- dbgc_dmp <- dbgexPhaseII <- dbgexExplicitEndInc <- dbgeEndDDEInvocatio  
  <- nImpl <- dbgeEndDDEInvocatio <- ksmdpg <- opidcl <- opidrv  
  <- sou2o <- opimai_real <- ssthrdmain <- main <- libc_start_main   
  <- start


Setting EVENT 10262:

When having a such error (ORA-600 [723]) set the event 10262. 

Set the following to ignore the error for small leaks (less than 500000 bytes):

ALTER SYSTEM SET EVENT='10262 trace name context forever, level 500000' SCOPE=SPFILE;

The instance must be restarted for the events to take effect.

CRITICAL: Failed to connect to database instance: ORA-12537: TNS:connection closed (DBD ERROR: OCIServerAttach)

CRITICAL: Failed to connect to database instance: ORA-12537: TNS:connection closed (DBD ERROR: OCIServerAttach)

The DB alert log show max processes exceeded.

ORA-00020: maximum number of processes (150) exceeded
ORA-20 errors will not be written to the alert log for
the next minute. Please look at trace files to see all
the ORA-20 errors.
Incremental checkpoint up to RBA [0x6c.3340f.0], current log tail at RBA [0x6c.34e88.0]
ORA-00020: maximum number of processes (150) exceeded
ORA-00020: maximum number of processes (150) exceeded
ORA-20 errors will not be written to the alert log for
ORA-20 errors will not be written to the alert log for
the next minute. Please look at trace files to see all
the next minute. Please look at trace files to see all
the ORA-20 errors.
the ORA-20 errors


SQL> show parameter processes;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
aq_tm_processes                      integer     1
db_writer_processes                  integer     1
gcs_server_processes                 integer     0
global_txn_processes                 integer     1
job_queue_processes                  integer     10
log_archive_max_processes            integer     4
processes                            integer     150
SQL> show parameter sessions;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
java_max_sessionspace_size           integer     0
java_soft_sessionspace_limit         integer     0
license_max_sessions                 integer     0
license_sessions_warning             integer     0
sessions                             integer     248
shared_server_sessions               integer
SQL>

===========================


SQL> alter system set processes=300 scope=both;

alter system set processes=300 scope=both
                 *
ERROR at line 1:
ORA-02095: specified initialization parameter cannot be modified


SQL> alter system set processes=300 scope=spfile;

System altered.

SQL> alter system set sessions=496 scope=spfile;

System altered.


- Bounce the database for changes to be effective