Database Is Consuming All The Real Memory When Users Access The Application
(Doc ID 799984.1)
Last updated on FEBRUARY 17, 2019
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 to 220.127.116.11.0 [Release 9.0.1 to 11.2]
IBM AIX on POWER Systems (64-bit)
z*OBSOLETE: IBM AIX 4.3 Based Systems (64-bit)
IBM AIX on POWER Systems (32-bit)
z*OBSOLETE: IBM AIX5L Based Systems (32-bit)
IBM AIX Based Systems (64-bit)IBM AIX5L Based Systems (32-bit)IBM AIX Based Systems (32-bit)IBM AIX 4.3 Based Systems (64-bit)
Database performance deteriorates after the databases and applications are started. Application users connect to the database using dedicated connections (though can also happen in shared server configuration). The memory consumption/ paging and swapping continues to grow until the system is unusable. Once the applications and databases are stopped the swap space is released and everything returns to normal.
Memory monitoring tools (e.g. Topas, NMON and vmstat) show Oracle processes have the highest memory usage.
No ORA-4030 errors are reported only the following are seen in the alert log:
ORA-27300: OS system dependent operation:fork failed with status: 12
ORA-27301: OS failure message: Not enough space
ORA-27302: failure occurred at: skgpspawn3.
The customer may have recently switched storage or otherwise made changes to their file systems.
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