Originally posted by reydp
Isn't it because auditing is for stadard SQL COMMANDS?
And packages/procedures that are derive from other source
like EXECUTE IMMEDIATE, IMMEDIATE here is an INTERNAL procedures that calls DBMS_SQL(native) commands prevent AUDITING from doing its task?
Just a wild idea. I would be very much glad if somebody can clear this thought ...
that could be, i could not find that documented though. that sucks though, you would think audit insert would audit insert when in reality some could easy cirumvent through an anonymous block