2.27 AUDIT_TRAIL
AUDIT_TRAIL
enables or disables database auditing.
Note:
This parameter is deprecated and applies only to traditional auditing. Traditional auditing is desupported starting in Oracle Database 23ai. Though traditional auditing is desupported, any current traditional audit settings that you have will still be honored. However, you cannot create new traditional audit settings. You can delete existing traditional audit settings. See Oracle Database Security Guide for more information about how this desupport works.
Property | Description |
---|---|
Parameter type |
String |
Syntax |
|
Default value |
|
Modifiable |
No |
Modifiable in a PDB |
No |
Basic |
No |
Values
-
none
Disables standard auditing. This value is the default if the
AUDIT_TRAIL
parameter was not set in the initialization parameter file or if you created the database using a method other than Database Configuration Assistant. If you created the database using Database Configuration Assistant, then the default isdb
. -
os
Directs all audit records to an operating system file. Oracle recommends that you use the
os
setting, particularly if you are using an ultra-secure database configuration. -
db
Directs audit records to the database audit trail (the
SYS.AUD$
table), except for records that are always written to the operating system audit trail. Use this setting for a general database for manageability.If the database was started in read-only mode with
AUDIT_TRAIL
set todb
, then Oracle Database internally setsAUDIT_TRAIL
toos
. Check the alert log for details. -
db, extended
Performs all actions of
AUDIT_TRAIL
=db
, and also populates the SQL bind and SQL text CLOB-type columns of theSYS.AUD$
table, when available. These two columns are populated only when this parameter is specified. When standard auditing is used withDB, EXTENDED
, then virtual private database (VPD) predicates and policy names are also populated in theSYS.AUD$
table.If the database was started in read-only mode with
AUDIT_TRAIL
set todb, extended
, then Oracle Database internally setsAUDIT_TRAIL
toos
. Check the alert log for details. -
xml
Writes to the operating system audit record file in XML format. Records all elements of the
AuditRecord
node exceptSql_Text
andSql_Bind
to the operating system XML audit file. -
xml, extended
Performs all actions of
AUDIT_TRAIL
=xml
, and includes SQL text and SQL bind information in the audit trail.
You can use the SQL AUDIT
statement to set auditing options regardless of the setting of this parameter.
In a CDB, the scope of the settings for this initialization parameter is the CDB. Although the audit trail is provided per PDB in a CDB, this initialization parameter cannot be configured for individual PDBs.
Examples
The following statement sets the db, extended
value for the AUDIT_TRAIL
parameter. The new value takes effect after the database is restarted.
SQL> alter system set AUDIT_TRAIL=db, extended scope=spfile; System altered. SQL>
The following statement sets the xml, extended
value for the AUDIT_TRAIL
parameter. The new value takes effect after the database is restarted.
SQL> alter system set AUDIT_TRAIL=xml, extended scope=spfile; System altered. SQL>
The following statement sets the db
value for the AUDIT_TRAIL
parameter. The new value takes effect after the database is restarted.
SQL> alter system set AUDIT_TRAIL=db scope=spfile; System altered. SQL>
See Also:
-
Oracle Database Security Guide for information about configuring unified audit policies
-
Oracle Database Upgrade Guide to learn more about traditional non-unified auditing