Audit Trails in Oracle APEX with Database Triggers and Session Metadata

Abstract

Audit trails in Oracle APEX applications must record both database-level changes and application-session context to support reliable investigation of user actions. Page-level logging alone can miss updates made through triggers, packages, scripts, or shared database routines, while trigger-only logging may capture changed values without explaining which APEX user, page, or session initiated the action. This article presents an audit trail implementation framework that combines database triggers with APEX session metadata for structured change capture. The framework records insert, update, and delete events with table name, primary key value, changed column, old value, new value, database user, APEX user, session ID, page ID, timestamp, and client context. The study shows that combining trigger-based capture with session metadata improves trace resolution, reduces missing user-context cases, and provides stronger evidence for administrative review. The proposed approach supports clearer accountability, faster change investigation, controlled audit storage, and more dependable audit reporting in Oracle APEX database applications.