FAQ: ORA-4030 (Doc ID 399497.1)

Last updated on JANUARY 09, 2024

Applies to:

Purpose

This article is intended to

• Help the reader understand causes of the ORA-4030
• Gather the diagnostics needed to narrow down the errors
• Answer some of the common questions asked about ORA-4030
• This is valid not only for ORA-4030 errors, but for any occurrence when the oracle database processes (user or background PGA) are suspected of consuming large amount of memory or potential memory leak.
• You may not get errors and just see high memory usage – ulimit on some platforms/versions no longer cause ORA-4030 to occur
• May get other errors such as ORA-12500
  ora-600 [729] (UGA memory) or ora-600 [730] (SGA or large pool)

********************************************************************************************************************************

There is now a Diagnostic Tool available through My Oracle Support to help diagnose ORA-4030 issues. 

This tool will provide suggestions to resolve ORA-4030 issues by analyzing uploaded RDA files. Individual processing of trace files or IPS packages is not currently implemented, but please check back since this functionality is planned for in an upcoming release. 

Select this link ORA-4030 Troubleshooting Tool to open a new browser window.

How to use the ORA-4030 Troubleshooting Tool on My Oracle Support <Document: 1511048.1>

********************************************************************************************************************************

Common Bugs

Unpublished Bug:6408917 Versions < 11 11.1.0.6 Backports possible Excessive PGA memory consumption can be seen when using ref cursors returned
from Java stored procedures. Ultimately this can lead to out of memory
errors such as:
ORA-29532: java call terminated by uncaught java exception: java.lang.outofmemory Unpublished Bug:6414844 Versions < 11.2 11.2 Backports possible to 10.1 memory may be wasted in a subheap using kghu memory allocation.

A heapdump will show free chunks in each extent with a "free" chunk which is
not quite large enough to satisfy a request. This is not really a memory
leak but inefficient use of memory in certain circumstances.
eg:
EXTENT 0 addr=0xb3810008
Chunk b3810010 sz= 16272 free " "  Wasted space
Chunk b3813fa0 sz= 16416 freeable "koh-kghu call "
Chunk b3817fc0 sz= 16416 freeable "koh-kghu call " ds=0xb7a1daf0
Chunk b381bfe0 sz= 16416 freeable "koh-kghu call " ds=0xb7a1daf0

Questions and Answers

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.