Database Reference
In-Depth Information
Audit succeeded.
SQL>
Query the DIRECT_PATH_NUM_COLUMNS_LOADED column of the UNIFIED_AUDIT_TRAIL to see
the audit history of activities that used the SQL*Loader direct path load method, for example:
SELECT DBUSERNAME, ACTION_NAME, OBJECT_SCHEMA, OBJECT_NAME, DIRECT_PATH_NUM_
COLUMNS_LOADED
FROM UNIFIED_AUDIT_TRAIL WHERE AUDIT_TYPE = 'DIRECT PATH API';
DBUSERNAME ACTION_NAME OBJECT_SCHEMA OBJECT_NAME DIRECT_PATH_NUM_COLUMNS_LOADED
----------- ----------- ------------- ------------ -----------------------------
-
HR INSERT HR REGIONS 6
Using Other Products with CDBs and PDBs—Database
Vault, Data Guard, LogMiner
There are other products that support the Oracle database and have configuration or
behavior differences in a multitenant environment. In this section we will introduce three
of these products—Database Vault, Data Guard, and LogMiner—and discuss how they
behave with CDBs and PDBs.
Database Vault
Oracle Database Vault is a tool that prevents privileged database users from accessing applica-
tion data using their system privileges. You can restrict a DBA's access so that they will not be
able to see sensitive information like social security numbers, salaries and bonuses, medical
records, financial information, or any other information deemed sensitive or confidential.
Oracle Database Vault Overview
The DBA can use Oracle Enterprise Manager Cloud Control 12 c or SQL*Plus to manage
Oracle Database Vault. Oracle Database Vault provides database roles that allow groups
of users to perform tasks based on separation of duties. DV_OWNER, DV_ADMIN,
and DV_ACCTMGR are the most commonly used roles. With the DV_OWNER and
DV_ADMIN roles you can create and manage Database Vault policies. You can manage
user accounts with DV_ACCTMGR.
Oracle Database Vault in a Multitenant Environment
In the multitenant environment each PDB has its own Database Vault metadata, including rule
sets and command rules. The objects in DVSYS and DVF common user schemas are available to
PDBs. You can create individual policies for each PDB, since the scope of the policies is local.
In the multitenant environment, the DVSYS schema is a common user schema that is
stored in the CDB$ROOT , and all the objects within the DVSYS schema are dependent on the
Search WWH ::




Custom Search