My Oracle Support Banner

How to purge GI files from ADR HOME in 12.1.0.2 and above (Doc ID 1969131.1)

Last updated on MARCH 07, 2022

Applies to:

Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Oracle Database - Standard Edition - Version 12.1.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.

Goal

The trace files in GI home is using up a large amount of disk space in ADR HOME, so some of those files are in need to be purged/deleted without affecting ADR rule.

Starting with the 12.1.0.2 release, Oracle Grid Infrastructure began using the Automatic Diagnostic Repository (ADR) to manage its alert log, diagnostic (trace) files, and related data.  All such data is now collected under an "ADR Home" directory, which for a GI installation on a given node has the form:
  <ORACLE_BASE>/diag/crs/<hostname>/crs
where
  <ORACLE_BASE> is the base file system location specified at install time.
  <hostname> is the unqualified IP hostname of the node.
(On Windows systems, backslashes are used rather than forward slashes.)

Unlike the Oracle database, GI does not have a background process that  purges old ADR data automatically.  All GI daemons use a trace file rotation scheme that limits each daemon to a fixed total amount of trace data, but command line programs (such as crsctl) do not.  Each execution of a command line program may, depending on the command and the result, produce a distinct trace file whose name includes the executable name and, for uniqueness, a numeric Operating System "process ID".  Over time, depending on command use and the amount of activity in the system, a large number of trace files (.trc) and their companion ADR metadata files (.trm) can accumulate in GI's ADR home.

If the file system that holds the ADR home becomes completely full, there is an exposure to various issues.  At minimum, new diagnostic and alert log data may fail to be preserved.  If other components are using the same file system, their functions may be impacted.  Therefore, GI's ADR diagnostic data that is older than a certain amount can and should be removed from time
to time to free up disk space in the file system.

Solution

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
Goal
Solution

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