My Oracle Support Banner

Bug 8560561 - audit TRIGGER RETURNS query instead of contents (Doc ID 1077396.1)

Last updated on FEBRUARY 23, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.2.0.0. [Release 11.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

In 11.1 and 11.2 if you have DDL/DML_AUDITING triggers written in PL/SQL, the code which produced the desired result in 10.2.0.4 stopped working in 11.1 and above

There are no errors but you will get something like the following instead of actual statement run.
for example:

SELECT A.SQL_TEXT FROM V$SESSION S,V$SQLAREA A WHERE S.SQL_HASH_VALUE=A.HASH_VALUE AND S.SQL_ADDRESS=A.ADDRESS AND S.SID=:B1

Whereas we should get the result of the above statement, not the statement itself, for example:

INSERT INTO EMP VALUES (<value1>, <value2>,....<value n>)

Business Impact
=============
Unable to implement DML AUDITING in 11g database, which was working fine in 10g

Changes

Upgraded to 11g

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.