PURGE AUDIT RECORDS OF ALL DATABASE_IDS BASED ON LAT DURING CLEAN_AUDIT_TRAIL WHEN NO DATABASE_ID PASSED (Doc ID 3059240.1)

Last updated on DECEMBER 30, 2024

Applies to:

Symptoms

SQL > sho parameter audit
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
audit_file_dest string /u01/app/oracle/admin/ULP1/adump
audit_sys_operations boolean TRUE
audit_syslog_level string
audit_trail string DB
unified_audit_common_systemlog string
unified_audit_sga_queue_size integer 1048576
unified_audit_systemlog string

SQL> select min(EVENT_TIMESTAMP), min(EVENT_TIMESTAMP_UTC) from unified_audit_trail;
MIN(EVENT_TIMESTAMP) MIN(EVENT_TIMESTAMP_UTC)
--------------------------------------------------------------------------- ---------------------------------------------------------------------------
21-AUG-24 05.21.36.286721 AM 21-AUG-24 05.21.36.286721 AM

SQL > select min(TIMESTAMP) from dba_audit_trail;
MIN(TIMES
---------
17-APR-22

-PDBs are cloned from other PDBs and ends up having records with multiple
DBID values and
-The purge job/CLEAN_AUDIT_TRAIL procedure is run without providing DBID
value (or) run with current DBID value.
-Because of this audit records of only current DBID are purged and customers
doesn’t know that they have to run purge operation explicitly for older DBID
values

Cause

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