Logstby Error When DBMS_AUDIT_MGMT Procedures Are Invoked For FGA_LOG$
(Doc ID 579038.1)
Last updated on FEBRUARY 04, 2020
Applies to:Oracle Audit Vault - Version 10.2.3 to 10.2.3
Oracle Database - Enterprise Edition - Version 10.2.0.3 to 10.2.0.3 [Release 10.2]
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.
DBMS_AUDIT_MGMT is a new package that is part of the management features of Audit Vault and is distributed as a patch you can apply on the source database.
Please use the following patches for the respective versions:
10.2.0.3 <patch 6989148> MLR ON TOP OF 10.2.0.3 FOR AUDIT TRAIL CLEAN-UP
10.2.0.4 <patch 6996030> MLR ON TOP OF 10.2.0.4 FOR AUDIT TRAIL CLEAN-UP
The Logical Standby package gets invalidated when one of the following APIs from DBMS_AUDIT_MGMT is invoked for DBMS_AUDIT_MGMT.AUDIT_TRAIL_FGA_STD or DBMS_AUDIT_MGMT.AUDIT_TRAIL_DB_STD or DBMS_AUDIT_MGMT.AUDIT_TRAIL_ALL:
In other words, when the FGA Audit table is involved in either DBMS_AUDIT_MGMT.INIT_CLEANUP or DBMS_AUDIT_MGMT.SET_AUDIT_TRAIL_LOCATION, because of the static reference in SYS.DBMS_INTERNAL_LOGSTDBY, the package gets invalidated.
Hence, an error similar to the following can be seen:
Any of the above patches is installed on the respective source database version.
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