Unified Audit Records Older Than 30 Days Are Not Purged Using DBMS_MGMT Purge Job
(Doc ID 2305499.1)
Last updated on MAY 24, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.1 to 12.2.0.1 [Release 12.1 to 12.2]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 Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
If the last_archive_time is set to anything greater than 30 days then the Purge Job doesn't delete all the data from Unified Audit Trail
However if it's changed from last_archive_time => SYSTIMESTAMP-31 to SYSTIMESTAMP-30 the Purge Job works as expected i.e. it deletes the audit data older than 30 days.
Changes
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 |
| References |