View – DBA – Security – Auditing
A user asked how to use SQL Developer to audit user XYZ. And to be honest, it’s not really set up to work that way. You define operations or objects you want audited. Any user that does XYZ to object ABC will get logged.
There’s an exception to this – you can setup SYSDBA users to be audited. This will grab the SYSDBA-level type operations that happen. Check out the latest docs here.
A Quick Example
I want to keep an eye on EMPLOYEES – the table. I trust my actual employees, of course.
So I go to the ‘Audited Objects’ page.
And this brings up a dialog to let me do just that:
The more you ask for, the more it costs. Keeping track of this stuff creates work for the database, so ask for what you need.
Once I have the EMPLOYEES table set to be ‘watched’, I only need to look at the Objects Trail.
So I go in as users HR and JSON and run a couple of SELECTS..then come back to my audit trail, and refresh the report.
Once this table gets fairly large, you’ll want to at least use FILTERs – if not perform maintenance on the audit logs themselves, a topic that’s not for this domain.