ORA-4031 with calls to ksfd_alloc_sgabuffer, ksfd_alloc_contig_buffer, ksfd_get_contig_buffer
(Doc ID 367392.1)
Last updated on FEBRUARY 04, 2022
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Error ORA-4031 is normally associated with lack of contiguous space in the shared pool, large pool, or numa pool. Traditionally, this error was reported due to a high volume of parsing activity in the shared pool, or high memory use due to parallel query, MTS, and/or IO Slaves. The scope of this note is not to explain the ORA-4031 error, but bring to the attention of the reader a new scenario for this error.
There is a new implementation in 10G when using Automatic Shared Memory Management (ASMM) and scattered reads that will trigger internal false ORA-4031 errors similar to that error shown below. When users enable events to dump errorstack traces for this error, a new entry will be reported in the alert.log file.
The goal of this note is to provide information to Database Administrators and Support Analyst on this new type of ORA-4031 error.
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