2.110 DIAGNOSTICS_CONTROL
DIAGNOSTICS_CONTROL enables you to control and monitor the users who perform potentially unsafe database diagnostic operations.
| Property | Description |
|---|---|
|
Parameter type |
String |
|
Syntax |
|
|
Default value |
|
|
Modifiable |
|
|
Modifiable in a PDB |
No |
|
Basic |
No |
|
Oracle RAC |
The same value must be used on all instances. |
When diagnosing Oracle database issues, an Oracle Support Service staff member might instruct you to perform diagnostic operations. Some diagnostic operations are harmless. However, others could have adverse effects if not performed properly with the guidance of an Oracle Support Service staff member. In order to control and monitor who performs such diagnostic operations, Oracle Database 21c introduces the following security controls:
- Potentially unsafe diagnostic operations are internally identified in the database. These operations include setting certain debug events and debug actions with the
ALTERSESSIONorALTERSYSTEMstatement. For example:ALTER SESSION SET EVENTS '1357 trace name context forever, level 2'; ALTER SYSTEM SET EVENTS 'trace[vos]'; - A user can be authorized to perform potentially unsafe diagnostic operations, either by being granted the
ENABLEDIAGNOSTICSsystem privilege, or by being granted theDBArole, or by authenticating asSYSDBA. - The
DIAGNOSTICS_CONTROLinitialization parameter enables you to specify how the database responds when an unauthorized user attempts to perform these diagnostic operations. The possible values are:ERROR: When an unauthorized user attempts to perform a potentially unsafe diagnostic operation, the attempt fails with errorORA-01031: insufficient privileges.WARNING: When an unauthorized user attempts to perform a potentially unsafe diagnostic operation, the attempt succeeds, but a warning is written to the alert log.IGNORE: When an unauthorized user attempts to perform a potentially unsafe diagnostic operation, the attempt succeeds and no error messages or warnings occur. This is the default.
Note:
When altering the DIAGNOSTICS_CONTROL initialization parameter, be aware of the following guidelines:
-
To modify this parameter with the
ALTERSYSTEMcommand, you must be authenticatedASSYSDBA. -
In Oracle RAC environments, it is currently not possible to modify this parameter on remote instances by specifying the
SIDclause in theALTERSYSTEMSETstatement.
Note:
This parameter is available starting with Oracle Database 21c.