Oracle Utilities - OCP: Oracle Database 12c Administrator Certified Professional - page 603

■ No column names are specified, so the database table column names are used.
■ The order of the columns match from the data file to the database table.
■ The datatypes are aligned.
■ It uses a comma as the field delimiter in the data file.
■ It uses a newline to indicate a new record.
■ It does not use quotes to enclose character fields.
■ The NLS client character set and NLS settings are used for date and timestamp data.
■ Constraints are enforced, and new rows do not overwrite existing data.
■ DEGREE_OF_PARALLELISM is AUTO , but it will be ignored if SQL*Loader switches to
direct path load.
Audit Operations
In Chapter 12, we introduced audit-related initialization parameters that have an impact on
PDBs and CDBs. In this section we will focus on the effect of audit operations on the utility
programs previously introduced in this chapter: Oracle Data Pump and Oracle SQL*Loader.
Both use unified auditing, where all audit records are centralized in one place, viewable in
one data dictionary view. But first we'll discuss audit policies in the multitenant environment,
focusing on the differences between CDB and PDB, or common and local auditing.
Local and Common Audit Policies
In the multitenant environment, you can set up local or common audit policies. This applies
to the AUDIT and NOAUDIT SQL statements as well as for unified audit policies.
The local audit policy can exist in either a PDB or CDB$ROOT . A local audit policy that
exists in CDB$ROOT can contain object audit options for local and common objects. Local
users who have the AUDIT_ADMIN role can enable local policies from their PDBs. Common
users with the role can enable local policies from the root or the PDB to which they have
privileges. The AUDIT_VIEWER role allows viewing and analyzing audit data.
The common audit policy is available to all PDBs in a CDB, can be enabled only for
common users, and can contain only info on common objects. Common audit policies can
only be created in CDB$ROOT , and only common users who have the AUDIT_ADMIN role
can create and maintain common audit policies.
Audit policies are by default local to the current PDB. To create a local or common
unified audit policy, follow this example:
SQL> CREATE AUDIT POLICY create_table_pol
2 PRIVILEGES CREATE ANY TABLE, DROP ANY TABLE
3 roles hr_admin, hr_system_admin;
Audit policy created.