RAC: instance crashes with ora-4031 as "gcs resources" and "gcs shadows" using large amount of shared pool (Doc ID 2132945.1)

Last updated on MAY 08, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Information in this document applies to any platform.

Symptoms

An instance crashed, and alert.log shows that ora-4031 as the cause of the instance crash.

Sat Apr 02 05:10:58 2016
ORA-04031 heap dump being written to trace file /home/oracle/RCINP/diag/rdbms/rcinp_b/RCINP2/trace/RCINP2_ora_2220.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
NOTE: ASMB terminating
Errors in file /home/oracle/RCINP/diag/rdbms/rcinp_b/RCINP2/trace/RCINP2_asmb_31174.trc:
ORA-04031: unable to allocate 4120 bytes of shared memory ("shared pool","unknown object","sga heap(1,0)","ASM extent pointer array")
Errors in file /home/oracle/RCINP/diag/rdbms/rcinp_b/RCINP2/trace/RCINP2_asmb_31174.trc:
ORA-04031: unable to allocate 4120 bytes of shared memory ("shared pool","unknown object","sga heap(1,0)","ASM extent pointer array")
ASMB (ospid: 31174): terminating the instance due to error 4031
Sat Apr 02 05:10:59 2016
System state dump requested by (instance=2, osid=31174 (ASMB)), summary=[abnormal instance termination].
System State dumped to trace file /home/oracle/RCINP/diag/rdbms/rcinp_b/RCINP2/trace/RCINP2_diag_31124_20160402051059.trc
Sat Apr 02 05:10:59 2016
License high water mark = 159
Instance terminated by ASMB, pid = 31174
USER (ospid: 38302): terminating the instance
Instance terminated by USER, pid = 38302

 

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