ASM failing with ORA-4031 caused by growth of 'ASM file' permanent allocations (Doc ID 602563.1)

Last updated on MARCH 19, 2009

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.3 to 11.1.0.7
This problem can occur on any platform.

Symptoms

The ASM instance fails with error ORA-4031. After restarting the instance, problem happens again few days later. Increasing the shared_pool_size parameter, only delays the error.

From the trace files generated by the automatic diagnostics for error ORA-4031, the memory allocations with comments 'ASM file' were the largest.

Memory Utilization of Subpool 1
================================
Allocation Name Size
_________________________ __________
"free memory " 29317936
"ASM file " 70201400



Because most of the memory allocated was type PERMANENT, it required enabling event 10235 level 65536 and restarting the instance.  Using a query over v$sgastat to identify the growing memory and then creating a heapdump level 536870914, together with a systemstate dump

select * from v$sgastat where name like 'ASM file%';

-- when there was a significant growth

sql> oradebug setmypid
sql> oradebug unlimit
sql> oradebug dump heapdump 536870914;
sql> oradebug tracefile_name
 


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms