Database Administration (MOSC)

MOSC Banner

dbms_audit_mgmt / use_last_arch_timestamp does not work?

edited Oct 4, 2018 11:12AM in Database Administration (MOSC) 2 commentsAnswered ✓

Hi All,

I observed that the dbms_audit_mgmt.clean_audit_trail does not work as expected.

Has anybody encounter the same issue?

My setup:

Oracle Database 12c Enterprise Edition - 12.2.0.1.0 64bit Production

select parameter, value from v$option where parameter like 'Unified Auditing';

PARAMETER                                                        VALUE

---------------------------------------------------------------- --------------------

Unified Auditing                                                 TRUE

SELECT min(EVENT_TIMESTAMP), max(EVENT_TIMESTAMP) FROM UNIFIED_AUDIT_TRAIL;

MIN(EVENT_TIMESTAMP)                                                        MAX(EVENT_TIMESTAMP)

--------------------------------------------------------------------------- ---------------------------------------------------------------------------

03-OCT-18 05.04.36.254576 PM                                                03-OCT-18 05.24.17.090625 PM

-- Set the last_archive_time

exec DBMS_AUDIT_MGMT.SET_LAST_ARCHIVE_TIMESTAMP(audit_trail_type => DBMS_AUDIT_MGMT.AUDIT_TRAIL_UNIFIED,last_archive_time => TO_TIMESTAMP('03-OCT-18 05.10.30 PM','dd-mon-yy hh.mi.ss AM'));

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center