My Oracle Support Banner

ORA-12853 / ORA-4031 or ORA-4030 on Instance Startup With increased SGA size (Doc ID 839789.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.3 to 11.1.0.7 [Release 10.2 to 11.1]
Information in this document applies to any platform.
***Checked for relevance on 29-Jul-2013***

Symptoms

System has high cpu count.

DB startup failed when trying to increase SGA_MAX_SIZE to higher value

o Error Pattern 1: Without LARGE_POOL_SIZE parameter

ORA-04030: out of process memory when trying to allocate 32 bytes (sql area,tmp)


o Error Pattern 2: With LARGE_POOL_SIZE parameter

ORA-12853: insufficient memory for PX buffers: current 0K, max needed 354288K
ORA-04031: unable to allocate 21544 bytes of shared memory ("large pool","unknown object","large pool","PX msg pool")

Changes

Trying to increase SGA_MAX_SIZE to larger size.

Cause

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
Symptoms
Changes
Cause
Solution
References

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