Configure Pure Mode of Unified Auditing in Oracle Database

-

 

Configure Pure Mode of Unified Auditing in Oracle Database

Unified Auditing provides a consolidated and streamlined auditing framework in Oracle Database. By default, Oracle operates in Mixed Mode, which means both traditional and unified auditing are enabled. If you want to use only Unified Auditing, you need to configure Pure Mode by relinking the Oracle binaries.

Below is a step-by-step guide to enable Pure Mode of Unified Auditing:

 Step 1: Check Current Unified Auditing Mode

Before making any changes, check whether Unified Auditing is currently enabled.sql


COL PARAMETER FORMAT A20
SET LINES 900
SELECT * FROM V$OPTION WHERE PARAMETER = 'Unified Auditing';

  • If the VALUE column shows TRUE, Unified Auditing is available (but not necessarily in pure mode).

  • We need to relink Oracle to fully switch to Pure Mode.

Step 2: Shutdown the Oracle Database

To relink the Oracle binaries, first shut down the database instance.

bash
sqlplus / as sysdba
SHUTDOWN IMMEDIATE;

 Step 3: Relink Oracle with uniaud_on Option

Navigate to the $ORACLE_HOME/rdbms/lib directory and relink the Oracle binaries with unified auditing enabled.

bash
cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk uniaud_on ioracle

Note: Ensure you have appropriate backup and necessary privileges before performing a relink.

 Step 4: Restart Oracle Database

Start the database back up using SQL*Plus:

bash
sqlplus / as sysdba
STARTUP;
EXIT;

Step 5: Verify Unified Auditing is Enabled in Pure Mode

Once the database is up, run the following command again to confirm Unified Auditing is active:

sql
SELECT * FROM V$OPTION WHERE PARAMETER = 'Unified Auditing';

If VALUE is still TRUE and the traditional audit parameters no longer work (like audit_trail), Pure Mode has been successfully enabled.

 Additional Notes:

  • In Pure Mode, traditional auditing settings (like audit_trail) are ignored.

  • You can manage audit policies using commands like CREATE AUDIT POLICY, AUDIT, and NOAUDIT.

  • Audit records are stored in the UNIFIED_AUDIT_TRAIL view.

Conclusion

Switching to Pure Mode of Unified Auditing centralizes and simplifies the auditing process in Oracle Database, improving performance and audit trail management. This setup is recommended for environments where audit compliance and centralized control are key requirements.

Happy auditing! 

Comments

Post a Comment

Popular posts from this blog

Configure Oracle Database Vault Realms

-
Configure Oracle Database Vault Realms to Secure the HR Schema Oracle Database Vault (DV) is a powerful security feature that enables fine-grained access control by enforcing security policies that protect sensitive data. One of the most important components in Database Vault is the Realm , which creates a security boundary around database objects to prevent unauthorized access — even by highly privileged users. In this blog, we’ll walk through the step-by-step process of configuring a Realm to secure the HR schema in an Oracle Database 19c environment. You’ll learn how to: Create a Realm Add objects to it Restrict access Enable auditing for security tracking What is a Realm? A Realm in Oracle Database Vault defines a logical security boundary around one or more database objects. Once a Realm is in place, no one — not even privileged users like DBAs — can access the protected objects without being explicitly authorized. Realms are ideal for: Securing sensitive ap...
Read more

Configure Transparent Database Encryption (TDE) in Oracle CDB

-
   Configure Transparent Database Encryption (TDE) in Oracle CDB Transparent Data Encryption (TDE) is a vital Oracle feature used to secure sensitive data at rest by encrypting database files. In this guide, we'll walk through configuring TDE in a CDB (Container Database) environment and demonstrate its effectiveness with a test tablespace and HR schema. Prerequisites Oracle Database (12c and above, preferably 19c or later) File system access to create wallets Appropriate privileges to administer TDE and manage tablespaces Step 1: Create a New Tablespace in PDB Connect to the PDB and create a new tablespace: sql SQL > CREATE TABLE SPACE userstab DATAFILE '/opt/oracle/oradata/XE/XEPDB1/userstab01.dbf' SIZE 1 G; Tablespace created. Step 2:Install the Sample HR Schema Install the sample HR schema into the newly created userstab tablespace: sql SQL > @? / demo / schema / human_resources / hr_main.sql This will create and populate HR sc...
Read more

Cloning Oracle E-Business Suite 12.2.11: RMAN + Rapid Clone

-
Cloning Oracle E-Business Suite (EBS) environments is a critical part of managing development, testing, and DR landscapes. In this post, we walk through the process of cloning EBS 12.2.11 from a production environment to a non-production one using RMAN active duplication and Oracle Rapid Clone utilities . Clone Scenario Source Database CDB : PRODCDB Source PDB : prod Target Database CDB : RNDCDB Target PDB : RND Step 1: Prepare the Target Server Create Required Directories mkdir -p /u01/oracle/RNDCDB mkdir -p /u01/oracle/RND mkdir -p /u01/oracle/clone_logs Verify Swap Space (Must be ≥ 16GB) free -h Step 2: Run Pre-Clone on Source Database Tier cd $ORACLE_HOME/appsutil/scripts/prod_PRODCDB perl adpreclone.pl dbTier Application Tier cd $ADMIN_SCRIPTS_HOME perl adpreclone.pl appsTier  Step 3: Clone the CDB with RMAN 3.1: Startup Target CDB in NOMOUNT Mode export ORACLE_SID=RNDCDB sqlplus / as sysdba STARTUP NOMOUNT; 3.2: Run RMAN Active Duplicate rman target sys@PRODCDB auxiliary sy...
Read more