Explain AUDIT ALL ON DEFAULT BY ACCESS; (Doc ID 2224619.1)

Last updated on FEBRUARY 02, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Information in this document applies to any platform.

Goal

Oracle support recommended the following from a previous closed SR:

If you pre-create a database and have audit_trail set to DB, when you say default audit policy enabled, I assume you mean " audit all by default by access" which you have in your existing DB,
Then you do an import, yes the table/object imported should considered as new objects created After the
audit all by default was defined, and it should capture the auditing records for
these objects.

So please test with create a test DB, have audit_trail set to DB, enable audit all by default by access ,
Do not enable any other auditing options like "audit update any table,,,,, audit insert any table".
Then export one table from source DB, and import that table to the new test DB, testing user activity
like insert, select, update ... Check the audit records.

Prior to a the full import I set the following option
AUDIT ALL ON DEFAULT BY ACCESS;

We are finding that the auditing is to extensive. Could you explain what the command actually does in terms of the range of auditing and type of statement level and object level auditing is enable after the import.
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms