Troubleshooting Ora-00600 Argument 723 Memory Leak

Troubleshooting ORA-600 [723] "PGA memory leak" Note: For additional ORA-600 related information please read Note 146580.1 PURPOSE: This article discusses the internal error "ORA-600 [723]", what it means and possible actions. The information here is only applicable to the versions listed and is provided only for guidance. ERROR: ORA-600 [723] [a] [b] VERSIONS: versions 6.0 to 11.1 DESCRIPTION: This is a memory leak in the Program Global Area (PGA) PGA is checked for Space leaks at logoff time and a leak was found. There is no data corruption with this error. ARGUMENTS: Arg [a] Logoff PGA size in bytes Arg [b] "memory leak" FUNCTIONALITY: MEMORY COMPONENT IMPACT: PROCESS FAILURE - but only during session delete so impact is minimal NON CORRUPTIVE - No underlying data corruption. SUGGESTIONS: Event 10262 can be set to safely ignore small memory leaks. Set the following in init.ora for example to disable space leaks less than 4000 bytes: event = "10262 trace name context forever, level 4000" and stop and restart the database. Repeated errors can be diagnosed further by sending the alert.log and trace files to Oracle Support Services. Known Issues: Bug# 6749617 See Note 6749617.8 OERI[723] of "Global Blockers" memory on disconnect Fixed: 10.2.0.5 Bug# 5891737 See Note 5891737.8 Dump (kcblsod) / OERI:723 / Memory leak in ASM/RAC Fixed: 10.2.0.4, 11.1.0.6, 10.2.0.3.P17

Bug# 5256703 See Note 5256703.8 OERI[723] due to memory leak in MMON Fixed: 11.1.0.6, 10.2.0.4.P17