2.25 AUDIT_SYS_OPERATIONS
AUDIT_SYS_OPERATIONS
enables or disables the auditing of directly issued user SQL statements with SYS
authorization. These include SQL statements directly issued by users when connected with the SYSASM
, SYSBACKUP
, SYSDBA
, SYSDG
, SYSKM
, or SYSOPER
privileges, as well as SQL statements that have been executed with SYS
authorization using the PL/SQL package DBMS_SYS_SQL
.
Note:
This parameter is deprecated and applies only to traditional auditing. Oracle strongly recommends against the use of this parameter. If you attempt to set this parameter, you will incur the following errors:
ORA-32004: obsolete or deprecated parameter(s) specified for
string
instance
ORA-32006: AUDIT_SYS_OPERATIONS initialization parameter has been deprecated
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 |
Boolean |
Default value |
|
Modifiable |
No |
Modifiable in a PDB |
No |
Range of values |
|
Basic |
No |
The audit records are written to the operating system's audit trail. The audit records will be written in XML format if the AUDIT_TRAIL
initialization parameter is set to xml
or xml, extended
On UNIX platforms, if the AUDIT_SYSLOG_LEVEL
parameter has also been set, then it overrides the AUDIT_TRAIL
parameter and SYS audit records are written to the system audit log using the SYSLOG
utility.
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.