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

Last updated on SEPTEMBER 26, 2012

Applies to:

Oracle Server - Enterprise Edition - Version 11.1.0.6 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 = /s00_11/app/oracle/diag/rdbms/oriont/oriont:
*************************************************************************
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  diag/rdbms/oriont/oriont/trace/oriont_j000_13161.trc
23-MAY-12 03:17:51  diag/rdbms/oriont/oriont/trace/oriont_j000_27758.trc
23-MAY-12 03:00:02  diag/rdbms/oriont/oriont/trace/oriont_j000_21333.trc
...
17-MAY-12 21:17:51  diag/rdbms/oriont/oriont/trace/oriont_j000_13573.trc
17-MAY-12 20:17:51  diag/rdbms/oriont/oriont/trace/oriont_j001_29626.trc
17-MAY-12 19:17:51  diag/rdbms/oriont/oriont/trace/oriont_j000_11759.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

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