ASM failing with ORA-4031 caused by growth of 'ASM file' permanent allocations
(Doc ID 602563.1)
Last updated on DECEMBER 25, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.3 to 11.1.0.7 [Release 10.2 to 11.1]Oracle Database Exadata 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.
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
================================
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
Cause
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
| Symptoms |
| Cause |
| Solution |