MOS Note For Bug 31562484 : Audit Options Changed After Database Upgrade to Higher versions (Doc ID 2787246.1)

Last updated on APRIL 21, 2023

Applies to:

Oracle Database - Enterprise Edition - Version 12.2.0.1 and later
Information in this document applies to any platform.

Symptoms

Audit option of unified audit policies changed after upgrade to higher version.

The minimum version of DB before upgrade should be 12.1.0.2. It means issue can be seen in the upgraded databases whose versions are 12.2.0.1/18c/19c/21c and does not containBug 31562484Bug 31562484Bug 31562484Bug 31562484 patch 31562484.

Note:

####

i) This issue cannot be seen on fresh installed database.

ii) The issue will not be seen if patch 31562484 applied before upgrade to higher versions

Example:
######

Please refer below example where audit option changed from ALL to ALTER DATABASE DICTIONARY after upgrade.

Before Upgrade:
##########

The unified auditing policy created with AUDIT_OPTION=ALL

SQL> create audit policy TEST_POLICY actions ALL;
Audit policy created.

SQL> audit policy TEST_POLICY;
Audit succeeded.
SQL>

SQL> select POLICY_NAME,AUDIT_OPTION,AUDIT_OPTION_TYPE from audit_unified_policies where policy_name = 'TEST_POLICY';
POLICY_NAME         AUDIT_OPTION            AUDIT_OPTION_TYPE
-------------------- ------------------------------ ------------------------------
TEST_POLICY           ALL                          STANDARD ACTION
SQL>

After Upgrade:
#########

The AUDIT_OPTION changed from ALL to ALTER DATABASE DICTIONARY

SQL> select POLICY_NAME,AUDIT_OPTION,AUDIT_OPTION_TYPE from audit_unified_policies where policy_name = 'TEST_POLICY';
POLICY_NAME         AUDIT_OPTION                                          AUDIT_OPTION_TYPE
-------------------- ---------------------------------------------------------------------------
TEST_POLICY         ALTER DATABASE DICTIONARY                     STANDARD ACTION

SQL>

Changes

Database upgrade to higher versions.The minimum version of DB before upgrade should be 12.1.0.2.It means version effected are 12.2.0.1,18c,19c & 21c. This bug is fixed in 23c.

11.2--> 12c/18c/19c/.. --> Issue not seen

12.1.0.2--> 12.2/18c/19c/.. --> Issue seen

12.2-->18c/19c/.. --> Issue seen

.. means we are referring to higher/future database versions.