Updating client scripts with the new Oracle home.

Resetting passwords to enforce case-sensitivity.

Run OPatch commands from the new Oracle home.

Setting threshold values for tablespace alerts.

Migration to unified auditing.

Upgrading user tables that depend on Oracle-maintained abstract data types.

RMAN uses the pull method to restore files using image copies

RMAN uses the push method to transfer image copies

RMAN uses the push method to transfer backup sets

RMAN uses the pull method to restore files using backup sets

creating a database link from CDB$ROOT in the local database to CDB$ROOT in the remote system that is to be cloned

creating a database link from CDB$ROOT in the local database to the PDB in the remote system that is to be cloned

backing up the cloned PDB

opening the cloned PDB

leaving the cloned PDB in mount state

to allow database duplication without a connection to the target instance.

to store backup metadata that would cause the controlfile to become too large.

to store backups that would cause the controlfile to become too large.

to report on the database schema at an earlier point in time.

to allow database duplication without a connection to the auxiliary instance.

Decreased use ofstorage to store audit trail rowsin the database.

It improves overall auditing performance.

It guarantees zero-loss auditing.

The audit trail cannot be easily modified because it is read-only.

It automatically audits Recovery Manager (RMAN) events.

log writer performance

database writer performance

general operating system health

SQL statements

database instance memory management and sizes

The entire PGA is located in the System Global Area (SGA) when using shared servers.

PGA_AGGREGATE_LIMIT is a hard limit on the PGA size for any one session.

The private SQL area (UGA) is located in the System Global Area (SGA) when using dedicated servers.

The private SQL area (UGA) is located in the System Global Area (SGA) when using shared servers.

Sorts and Hash Joins use PGA memory.