Agent Core Dumps in perl Due to High Memory Utilization and Circular IFILE Reference (Doc ID 1916023.1)

Last updated on NOVEMBER 04, 2014

Applies to:

Enterprise Manager for Oracle Database - Version 12.1.0.2.0 to 12.1.0.5.0 [Release 12.1]
Enterprise Manager Base Platform - Version 12.1.0.3.0 and later
Information in this document applies to any platform.

Symptoms

12c Agent generates huge core dump file of size 60GB to 100 GB, which uses up the disk space completely at the Agent mount point:

-r--------+ 1 oracle oinstall 108493627392 Aug  1 23:41 core.67864
-r--------+ 1 oracle oinstall 108491456512 Aug  2 10:21 core.120915

This occurred usually once per day, but at different times of the day.

Generating the stack trace from the Core file using the steps in <Note 1812.1> - TECH: Getting a Stack Trace from a CORE file, returns:

Loaded symbols for
/u01/app/oracle/product/EMbase/core/12.1.0.3.0/perl/lib/5.10.0/x86_64-linux-thread-multi/auto/Encode/Encode.so
Core was generated by
`/u01/app/oracle/product/EMbase/core/12.1.0.3.0/perl/bin/perl/u01/app/oracle/pr'.
Program terminated with signal 11, Segmentation fault.
#0  0x00000000004513f4 in S_save_magic ()
(gdb) bt
#0  0x00000000004513f4 in S_save_magic ()
#1  0x00000000004518b1 in Perl_mg_length ()
#2  0x0000000000475aa5 in Perl_sv_len ()
#3  0x000000000048f018 in Perl_pp_length ()
#4  0x000000000046801e in Perl_runops_standard ()
#5  0x000000000046484d in perl_run ()
#6  0x000000000041ed7c in main ()
(gdb) quit

The above indicates that the core file is generated when Agent is executing a perl script.
There are however no errors reported in the Agent logs at the time of the core file generation.

 

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