My Oracle Support Banner

E-AD: Database Level Auditing Using Trigger Does Not Insert OPRID Info. (Doc ID 2691653.1)

Last updated on JULY 18, 2020

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.56 and later
Information in this document applies to any platform.

Symptoms

On : 8.56 version, Application Designer

ACTUAL BEHAVIOR
---------------
RDBMS Database level auditing using trigger does not insert OPRID in 2 tier

Using Database level auditing to capture changes to sensitive fields.

Setup a trigger using Database level auditing to capture changes made to vendor bank account online as well as by using SQL Developer.

The OPRID of the use making the change ONLINE is correctly captured by the trigger.

The OPRID of the user making the change via SQL Developer is not captured by the trigger.


Oprid info. should be captured when changes made via SQL developer.


Using Database level auditing triggers to capture audit info.



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
Cause
Solution


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