How to Identify if Unified Audit Entries were Generated on Primary or Standby Database?
(Doc ID 2714585.1)
Last updated on SEPTEMBER 27, 2020
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Information in this document applies to any platform.
Identify if unified audit entries were generated on primary or standby database when querying UNIFIED_AUDIT_TRAIL view from Standby database.
The audit entries generated in primary database will be replicated to the standby, and the standby database will include entries from both sources, primary records + any audit entry generated in the standby stored as .bin files (when the standby is open in read only mode).
When the database is not writable (such as during database mounts), if the database is closed, or if it is read-only, then Oracle Database writes the audit records to these external files. The default location for these external files is the $ORACLE_BASE/audit/$ORACLE_SID directory. The UNIFIED_AUDIT_TRAIL view gets the audit records from both database store and the OS .bin files.
However, UNIFIED_AUDIT_TRAIL view does not include a column that reference the source database where the audit entry was generated from.
USERHOST column will capture the client host but it will not identify if it was triggered on the primary or the standby db.
Unpublished Bug 31916720 : HOW TO IDENTIFY AUDIT ENTRY GENERATED IN PRIMARY OR STANDBY
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