How To Audit Application Username Using Trigger
Last updated on JUNE 19, 2017
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Information in this document applies to any platform.
Checked for relevance on 21-May-2013
How to audit application username using trigger. For example if an application user updates/inserts/deletes some data through application client and you want to store transaction details such as application username, old values for the columns, date & time etc.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms