ASM Instance ORA-04031: unable to allocate 232 bytes of shared memory (“shared pool”,”select ks.inst_id,ksuxsins,k…”,”KKSSP^2431″,”kglpn”)

One of the +ASM instance alert log has ORA-04031 errors:

2025-07-17T23:00:48.475567+10:00
Errors in file /u01/app/grid/diag/asm/+asm/+ASM1/trace/+ASM1_ppa7_64031.trc (incident=160513):
ORA-04031: unable to allocate 2072 bytes of shared memory ("shared pool","unknown object","sga heap(1,0)","parameter table block")
Incident details in: /u01/app/grid/diag/asm/+asm/+ASM1/incident/incdir_160513/+ASM1_ppa7_64031_i160513.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
2025-07-17T23:00:48.550908+10:00
ORA-04031 heap dump being written to trace file /u01/app/grid/diag/asm/+asm/+ASM1/incident/incdir_160513/+ASM1_ppa7_64031_i160513.trc

CAUSES

The SGA_TARGET or MEMORY_TARGET parameter setting is too small.


SQL> SELECT INST_ID, POOL, NAME, BYTES/1024/1024 "SPACE MB"
FROM gv$sgastat
WHERE name = 'free memory'
AND POOL = 'shared pool'
ORDER BY INST_ID;


INST_ID POOL NAME SPACE MB
---------- -------------- ------------------------------ ----------
1 shared pool free memory 195.44057
2 shared pool free memory 115.6167
3 shared pool free memory 92.235062

RESOLUTION

Increase size of parameter SGA_TARGET or MEMORY_TARGET.

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.