In this Document
Oracle Server - Enterprise Edition - Version: 184.108.40.206 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Sometimes there is no alert log available or the ORA-4031 is not
reported in the alert log. The incident trace file is available but it
does not include subpool information.
This note is intended to help in diagnosing these cases.
The incident trace file in 11g reports the parameter values including
their current values achieved by ASMM/AMM (double underscore parameters)
at the time of error.
ORA-04031: unable to allocate 2048024 bytes of shared memory ("large pool","unknown object","large pool","PX msg pool")
The trace file of above error contains:
The problem here is the low free memory in the large pool.
As we see in trace file the large pool has grown up to nearly 1GB dynamically (SGA_TARGET is 1.6GB).
The suggestion would be to increase the SGA_TARGET value. This will require an outage for the database.
ORA-04031 error on shared pool.
The trace file contains:
Determine the sum of auto tuned components of SGA and PGA_AGGREGATE_TARGET.
Auto-tuned values for Shared Pool and Buffer Cache add up to 4,630,511,616 (just under SGA_TARGET).
is used here so PGA and SGA are auo-tuned by the database.
MEMORY_TARGET minus SGA_TARGET leaves 5,838,471,168. The auto-tuner had
the PGA_AGGREGATE_TARGET set up to 9,059,969,640 at some point. That
would be a problem trying to get that much PGA memory on top of the
almost 5G SGA_TARGET.
MEMORY_TARGET needs to be increased to accommodate the workload needs for SGA and PGA.
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/38267/viewspace-715736/，如需转载，请注明出处，否则将追究法律责任。