My Oracle Support Banner

How To Audit Application Username Using Trigger (Doc ID 443724.1)

Last updated on APRIL 03, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 9.2.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Checked for relevance on 21-May-2013

Goal

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.

Solution

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
Goal
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.