My Oracle Support Banner

Empty "core_<nnnn> Directories Getting Created Periodically in $ORACLE_HOME/dbs With No Alert Log or Application Errors (Doc ID 2285409.1)

Last updated on NOVEMBER 11, 2019

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database 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.


Empty directories of the form 'core_<nnnn>' where <nnnn> is an integer representing the dumping process PID were being created periodically every 12 hours in the $ORACLE_HOME/dbs directory.

There were no corresponding errors in the alert log, nor with any other application or service associated with the database. The database was running on a Redhat Linux x86-64 server.

The system messages log showed that a process known as the ABRT daemon was deleting the core files. The ABRT daemon is responsible for handling the application cores created by segmentation faults.
By default it will reject cores from applications that don't have a known GPG signature. Once this behavior was changed, the core files were not deleted and were available for analysis. The stack showed:

The function getgrnam_r() is an operating system call:

$ man getgrnam_r

getgrnam, getgrnam_r, getgrgid, getgrgid_r - get group file entry

The core file also showed that the dumping process was called 'oracledelphix_sid'.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.