This content has been marked as final. Show 6 replies
the feature you are using seems to be ultimately mapped to a database feature called array insert and what you are
observing is not a bug, in this case the binds being shown are only for the LAST array bind value in a single audit record.
An array insert is akin to an "insert as select" operation in that it can create many rows in a single execution.
This information comes from diagnosing a similar problem in Bug 15932553 (not a bug),
Harm ten Napel
After analising your answer I re-read the documentation. Your right, that's explicit on footnote1:
Columns with an asterisk (*) in Table 6-2 appear in the audit records only if you have set the AUDIT_TRAIL initialization parameter to DB_EXTENDED or XML, EXTENDED. Also, for an array, the values recorded are only the last set of bind values.
It just makes me wonder why isn't a way to override this... seems to me that oracle audit can work properly on any real world application