when procedure executed in SQLPLUS it generates audit in SYS.AUD$
when it executed from DBMS_JOB, no audit is generated any ideas?
tables are audited by access for insert and update
Do I have to enable sys auditing to get it to work?
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 ...
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
Originally posted by eugene when procedure executed in SQLPLUS it generates audit in SYS.AUD$
when it executed from DBMS_JOB, no audit is generated any ideas?
tables are audited by access for insert and update
Do I have to enable sys auditing to get it to work?
Why don't you raise a tar and post the results here, I'd be curious to see what theose redwood shores prima donna's have to say
Originally posted by stmontgo 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
If this is the case, then oracle now can include this for there new patches or maintenance release. Or worse comes to worst have to wait for new version, maybe something like 11d(after 10g).
Bookmarks