My Oracle Support Banner

Client_identifier Isn't Being Popoulated Using FGA Policies With UNIFIED_AUDIT_TRAIL (Doc ID 2675842.1)

Last updated on JUNE 30, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 to 19.7.0.0.0 [Release 12.1 to 19]
Information in this document applies to any platform.

Symptoms

The client_identifier isn't being populated when using FGA policies with UNIFIED_AUDIT_TRAIL

Changes

Example:

Create and enable a policy:


begin
dbms_fga.add_policy(
object_schema=>'SCOTT',
object_name=>'TEST_TABLE',
policy_name=>'SCOTT_1',
audit_column=>'Column_1,Column_2,Column_3,Column4',
statement_types=>'INSERT, UPDATE , DELETE , SELECT',
audit_column_opts=>DBMS_FGA.ANY_COLUMNS);
end;

 

Logon on to database instance and set the client_identifier:


exec DBMS_SESSION.SET_IDENTIFIER('random.user')


Run some queries involving monitored table:


select * from scott.test_table
select * from scott.test_table where Column_3='RVALUE'


Then query the unified_audit_trail:


select * from unified_audit_trail
where terminal ='ANYTERMINALNAME'
order by event_timestamp desc

The CLIENT_IDENTIFIER column is not getting populated.

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.