How do you validate that the database was migrated to Unified Auditing?

Unified Auditing is enabled at database creation or migration in 23ai. Let’s analyze:

A . By querying V$OPTION for parameter Unified Auditing.

True. SELECT VALUE FROM V$OPTION WHERE PARAMETER = 'Unified Auditing'; returns TRUE if

enabled. It’s the definitive way to confirm Unified Auditing is active at the database level.

Mechanics:V$OPTION reflects compiled-in features; TRUE indicates the binary was linked with

Unified Auditing (uniauflt=on during relink).

Practical Use:Quick, reliable check post-migration or upgrade.

B . By using the LSINVENTORY Command to query the Oracle Database Software Library.

False. LSINVENTORY (from OPatch) lists installed software components, not runtime features like

auditing mode.

C . By querying the DBA_UNIFIED_AUDIT_OPTION view.

False. This view doesn’t exist; DBA_AUDIT_POLICIES or UNIFIED_AUDIT_TRAIL show policies and

records but not migration status.

D . By executing DBMS_AUDIT_MGMT PL/SQL package in Verify mode.

False. No “Verify mode” exists in DBMS_AUDIT_MGMT; it manages audit trails, not migration

validation.

Reference:Oracle Database Security Guide 23ai, "Verifying Unified Auditing."