Oracle教程 2023-02-23

Oracle 视图 DBA_AUDIT_EXISTS 官方解释，作用，如何使用详细说明

本站中文解释

Oracle视图DBA_AUDIT_EXISTS是用来查询已存在的审计记录的视图，旨在支持对用户帐户进行审计。在查询审计信息时，可以使用此视图的审计策略名称、日期和时间、地址以及SYS_CONTEXT 列（应用于自定义审计事件）来识别所需的审计记录。

使用方法：

1. 首先，用户可以查询此视图，以验证已启用哪些审计策略：

SELECT policy_name FROM dba_audit_exists;

2. 用户还可以提供一个审计策略的名称，查询该策略的详细审计信息：

SELECT * FROM dba_audit_exists
WHERE policy_name = ‘POLICY_NAME’;

3.用户还可以使用视图中的SYS_CONTEXT 列来查询自定义审计策略的详细审计信息：

SELECT * FROM dba_audit_exists
WHERE sys_context = ‘CUSTOM_AUDIT_POLICY’;

官方英文解释

DBA_AUDIT_EXISTS displays audit trail entries produced by AUDIT EXISTS and AUDIT NOT EXISTS.

Note:

This view is relevant when using traditional auditing. Traditional auditing is deprecated in Oracle Database 21c. Oracle recommends that you instead use unified auditing, which enables selective and more effective auditing inside Oracle Database.

See Oracle Database Security
Guide for more information about unified auditing.
See Oracle Database Upgrade
Guide for more information about migrating to unified auditing.

This view is populated only in an Oracle Database where unified auditing is not enabled. When unified auditing is enabled in Oracle Database, the audit records are populated in the new audit trail and can be viewed from UNIFIED_AUDIT_TRAIL.

Column	Datatype	NULL	Description
`OS_USERNAME`	`VARCHAR2(255)`		Operating system login username of the user whose actions were audited
`USERNAME`	`VARCHAR2(128)`		Name (not ID number) of the user whose actions were audited
`USERHOST`	`VARCHAR2(128)`		Client host machine name
`TERMINAL`	`VARCHAR2(255)`		Identifier of the user’s terminal
`TIMESTAMP`	`DATE`		Date and time of the creation of the audit trail entry (date and time of user login for entries created by `AUDIT SESSION`) in the local database session time zone
`OWNER`	`VARCHAR2(128)`		Intended creator of the non-existent object
`OBJ_NAME`	`VARCHAR2(128)`		Name of the object affected by the action
`ACTION_NAME`	`VARCHAR2(28)`		Name of the action type corresponding to the numeric code in the `ACTION` column in `DBA_AUDIT_TRAIL`
`NEW_OWNER`	`VARCHAR2(128)`		Owner of the object named in the `NEW_NAME` column
`NEW_NAME`	`VARCHAR2(128)`		New name of an object after a `RENAME` or the name of the underlying object
`OBJ_PRIVILEGE`	`VARCHAR2(32)`		Object privileges granted or revoked by a `GRANT` or `REVOKE` statement. The value of this column is a 32-character string of `Y` and dash (`-`) characters. Each character corresponds to a numbered privilege in the following list. The left-most character corresponds to privilege 0, the next character corresponds to privilege 1, and so on. The right-most character corresponds to privilege 31. 0 – `ALTER` 1 – `AUDIT` 2 – `COMMENT` 3 – `DELETE` 4 – `GRANT` 5 – `INDEX` 6 – `INSERT` 7 – `LOCK` 8 – `CREATE` 9 – `SELECT` 10 – `UPDATE` 11 – `REFERENCES` 12 – `EXECUTE` 13 – `VIEW` 14 – `DROP` 15 – `ANALYZE` 16 – `CREATE` 17 – `READ` 18 – `WRITE` 19 – `KEEP` `SEQUENCE` 20 – `ENQUEUE` 21 – `DEQUEUE` 22 – `UNDER` 23 – `ON` `COMMIT` 24 – `REWRITE` 25 – `UPSERT` 26 – `DEBUG` 27 – `FLASHBACK` 28 – `MERGE` 29 – `USE` 30 – `FLASHBACK` `ARCHIVE` 31 – `DIRECTORY` `EXECUTE` A `Y` indicates that the privilege was granted or revoked by the statement. A dash indicates that the privilege was not affected by the statement. For example, the following value indicates that the `MERGE` privilege was granted or revoked by the statement: `----------------------------Y---`
`SYS_PRIVILEGE`	`VARCHAR2(40)`		System privileges granted or revoked by a `GRANT` or `REVOKE` statement
`GRANTEE`	`VARCHAR2(128)`		Name of the grantee specified in a `GRANT` or `REVOKE` statement
`SESSIONID`	`NUMBER`	`NOT NULL`	Numeric ID for each Oracle session
`ENTRYID`	`NUMBER`	`NOT NULL`	Numeric ID for each audit trail entry in the session
`STATEMENTID`	`NUMBER`	`NOT NULL`	Numeric ID for each statement run
`RETURNCODE`	`NUMBER`	`NOT NULL`	Oracle error code generated by the action. Some useful values: `0` – Action succeeded `2004` – Security violation
`CLIENT_ID`	`VARCHAR2(128)`		Client identifier in each Oracle session
`ECONTEXT_ID`	`VARCHAR2(64)`		Application execution context identifier
`SESSION_CPU`	`NUMBER`		Amount of CPU time used by each Oracle session
`EXTENDED_TIMESTAMP`	`TIMESTAMP(6) WITH TIME ZONE`		Timestamp of the creation of the audit trail entry (timestamp of user login for entries created by `AUDIT SESSION`) in UTC (Coordinated Universal Time) time zone
`PROXY_SESSIONID`	`NUMBER`		Proxy session serial number, if an enterprise user has logged in through the proxy mechanism
`GLOBAL_UID`	`VARCHAR2(32)`		Global user identifier for the user, if the user has logged in as an enterprise user
`INSTANCE_NUMBER`	`NUMBER`		Instance number as specified by the `INSTANCE_NUMBER` initialization parameter
`OS_PROCESS`	`VARCHAR2(16)`		Operating System process identifier of the Oracle process
`TRANSACTIONID`	`RAW(8)`		Transaction identifier of the transaction in which the object is accessed or modified
`SCN`	`NUMBER`		System change number (SCN) of the query
`SQL_BIND`	`NVARCHAR2(2000)`		Bind variable data of the query
`SQL_TEXT`	`NVARCHAR2(2000)`		SQL text of the query
`OBJ_EDITION_NAME`	`VARCHAR2(128)`		Name of the edition containing the audited object

Note:

The SQL_BIND and SQL_TEXT columns are only populated if the AUDIT_TRAIL initialization parameter is set to db, extended.

本站中文解释

官方英文解释

相关推荐