My Oracle Support Banner

FAQ: ORA-4030 (Doc ID 399497.1)

Last updated on MARCH 27, 2020

Applies to:

Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 8.1.5.0 and later
Information in this document applies to any platform.

Purpose

This article is intended to

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

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>

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

Note:
If you would like to explore this topic further, please join the Community discussion 'Diagnosing and Resolving ORA-4030 errors' where you can ask questions, get help from others, and share your experiences with this specific article.

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

To view full details, sign in with your My Oracle Support account.

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


In this Document
Purpose
 Common Bugs
Questions and Answers
 What is an ORA-4030?
 What is difference between 4030 and 4031?
 What are the contents of Program Global Area memory?
 Why do I see processes growing larger than the PGA_AGGREGATE_TARGET/MEMORY_TARGET/MEMORY_MAX/TARGET?
 Can you control the size of a process?
 Can you limit the size of a process?
 What information needs to be gathered to diagnose?
 Why does my code give ORA-4030 when run through listener connection, but not local connection?
 What to look at in RDA?
 What kernel or shell limits need to be checked?
 How to monitor pga usage from within the database?
 How to monitor memory usage from the OS on UNIX/Linux?
 How to monitor memory usage from the OS on MS-Windows?
 Why do we still get ORA-4030 or ORA-12500 on MS-Windows 32 bit database after adding more RAM?
 How to create a heapdump?
 What heapdump level to gather?
 See high amount of 'perm' allocations. When to set 10235 event?
 Platform Specific Configurations leading to memory problems
 All 64 bit unix/linux platforms - 16G pga size limit with realfree memory allocator
 Community discussion
References

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