My Oracle Support Banner

ADRCI Auto Deletion Of Trace Files Doesn't Work (Doc ID 1491619.1)

Last updated on JULY 24, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.6 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 Backup Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

ADRCI is not purging the trace files according to the control settings.

The LAST_AUTOPRG_TIME in SHOW CONTROL output is updated:

adrci> host "date"
Mon May 21 11:40:58 EEST 2012
adrci> show control
ADR Home = <ADR_HOME Path>:
*************************************************************************
ADRID                SHORTP_POLICY        LONGP_POLICY         LAST_MOD_TIME                            LAST_AUTOPRG_TIME                        
LAST_MANUPRG_TIME                        ADRDIR_VERSION       ADRSCHM_VERSION      ADRSCHMV_SUMMARY     ADRALERT_VERSION     CREATE_TIME
-------------------- -------------------- -------------------- ---------------------------------------- ----------------------------------------
---------------------------------------- -------------------- -------------------- -------------------- -------------------- ----------------------------------------
192390676            168                  720                  2012-04-17 14:16:19.418774 +02:00        2012-05-21 00:29:41.740629 +02:00
                                         1                    2                    80                   1                    2009-03-18 12:08:30.251893 +02:00


However, the adrci command "show tracefile -rt" shows many JXXX trace files which are not purged automatically:

adrci> show tracefile -rt
23-MAY-12 04:17:51 <ADR_HOME>/trace/<SID>_j000_<PID>.trc
23-MAY-12 03:17:51 <ADR_HOME>/trace/<SID>_j000_<PID>.trc
23-MAY-12 03:00:02 <ADR_HOME>/trace/<SID>_j000_<PID>.trc
...
17-MAY-12 21:17:51 <ADR_HOME>/trace/<SID>_j000_<PID>.trc
17-MAY-12 20:17:51 <ADR_HOME>/trace/<SID>_j000_<PID>.trc
17-MAY-12 19:17:51 <ADR_HOME>/trace/<SID>_j000_<PID>.trc

Changes

From the alert file we can see that the fixed_date instance parameter is set and unset every minute:

Sun May 20 13:03:12 2012
ALTER SYSTEM SET fixed_date='NONE' SCOPE=MEMORY;
ALTER SYSTEM SET fixed_date='2012-07-17-13:03:12' SCOPE=MEMORY;
Sun May 20 13:04:12 2012
ALTER SYSTEM SET fixed_date='NONE' SCOPE=MEMORY;
ALTER SYSTEM SET fixed_date='2012-07-17-13:04:12' SCOPE=MEMORY;
...
Wed May 23 15:08:12 2012
ALTER SYSTEM SET fixed_date='NONE' SCOPE=MEMORY;
ALTER SYSTEM SET fixed_date='2012-07-20-15:08:12' SCOPE=MEMORY;
Wed May 23 15:09:12 2012
ALTER SYSTEM SET fixed_date='NONE' SCOPE=MEMORY;
ALTER SYSTEM SET fixed_date='2012-07-20-15:09:12' SCOPE=MEMORY;

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
Changes
Cause
Solution

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