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.

Recovery begins from the beginning of the CURRENT redo log group.

Recovery begins from the last checkpoint position that was calculated by the Database Writer before instance failure.

Recovery begins from the start of any ACTIVE redo log group or the start of the CURRENT log group if no other group is ACTIVE.

Recovery reads redo until the end of the redo thread. SMON rolls back any dead transactions, and then the datanase is opened.

Recovery begins from the last checkpoint position that was recorded in the control file by the checkpoint process (CKPT).

Recovery reads redo until the end of the redo thread, and then opens the database. SMON then rolls back any dead transactions.

An application root clone gets created automatically.

The upgrade can be performed when connected either to CDB$ROOT or to PDB$SEED.

After an application upgrade, the application container's PDBs remain synchronized with the existing application root.

The upgrade must be performed when connected to CDB$ROOT.

An application name and version number must be specified to upgrade the application.

After an application upgrade, the application container's PDBs are automatically synchronized with the application root clone.

It succeeds and creates multisection backup sets that are used for active database duplication.

It fails because there is no connection to a recovery catalog.

It succeeds only if the target database is in MOUNT state.

It fails because no parallel channels are allocated for the auxiliary database.

It will create ‘$ORACLE_HOME/dbs/cdb1/CDB1/controlfile02.ctl’

It will create ‘/u01/app/oralce/oradata/CDB1/controlfile/controlfile02.ctl’.

It will re-create ‘/u02/app/oracle/fast_recover_area/cdb1/CDB1/controlfile02.ctl’

It will create ‘/u01/app/oracle/product/12.2.0.1/db_1/dbs/snapcf_cdb1control02.ctl’.

It will fail because there is no autobackup of the controlfiles.

They can be gathered by the DBMS_STATE package.

They are ignored by Optimizer if they are state.

They are gathered by the SQL Tuning Advisor.

By default, they are automatically gathered by a maintenance job.

They provide real-time data about schema objects.

AWR snapshots can be created in CDB$ROOT.

ADDM can run in a nonroot container.

AWR reports can be generated while connected to any container.

All AWR data is stored in the CDB$ROOT SYSAUX tablespace.

AWR snapshots can be created in a PDB.

No AWR data is stored in the CDB$ROOT SYSAUX tablespace.

The four sections must be image copies.

Each of the file sections must be processed serially.

The four sections must be contained in backup sets.

The four sections can be created in parallel.

The four sections can be created serially.

It will return an error because creation of a local role is not allowed in CDB$ROOT.

ROLE1 will be created only in CDB$ROOT.

It will return an error because common roles must start with C##.

ROLE1 will be created only in CDB$ROOT and APP1_ROOT.

ROLE1 will be created in CDB$ROOT, PDB1, APP1_ROOT, and APP1_PDB1.

V$SERVICE_EVENT displays wait counts for every wait event for each service even including counts of zero for waits that never occurred.

V$SESSION_WAIT and V$SESSION both contain details of the event on which a non-waiting session last waited.

V$SESSION_WAIT and V$SESSION both contain details of the event on which a waiting session is currently waiting.

V$SESSION_EVENT displays all waits events for those events that have occurred at least once for sessions that have now terminated.

V$SESSION_WAIT_CLASS displays waits broken down by wait class only for terminated sessions.

Tablespaces always remain in read/write mode during transportable tablespace operations.

Tablespaces never remain in read/write mode during transportable tablespace operations.

A transportable data pump import can leave a plugged-in tablespace in read-only mode.

Simultaneous data pump jobs can be limited at the pluggable database (PDB) level.

A transportable data pump import can leave a plugged-in tablespace in read/write mode.

An ordinary data pump export of a table with encrypted columns will always encrypt the same columns when imported.

The ORA_ARCHIVE_STATE column may only be queried by users with the DBA role set.

The ORA_ARCHIVE_STATE column is only displayed if it is referenced in the column select list of a query

The ROW ARCHIVAL VISIBILITY session parameter defaults to active rows.

The ORA_ARCHIVE_STATE column may only be updated by users with the DBA role set.

The ORA_ARCHIVE_STATE column is updated in an overnight maintenance job based on activity tracking.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to CDB$ROOT gathers object statistics in all open PDBs except PDB$SEED.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to a PDB opened in read/ write mode gathers object statistics for that PDB.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to CDB$ROOT gathers object statistics only in CDB$ROOT.

System statistics can be gathered only while connected to CDB$ROOT.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to CDB$ROOT gathers object statistics in all open pluggable databases (PDBs)

It has the same common users defined as does CDB1.

It has only local roles.

It has the same number of roles as CDB1.

Service PDB1 is created for remote logins to PDB1.

It is in mount state after creation.

It has no local users.

The number of table rows is considered when evaluating the cost of accessing a table using an index.

Index balanced B*Tree height is considered when evaluating the cost of using an index.

The Statistics Advisor can help recommend the best way to gather statistics.

Statistics collected using DBMS_STATS always yield the best optimizer result.

The Statistics Advisor generates actions for all recommendations.

by performing emergency monitoring using Real-Time Automatic Database Diagnostic Monitor (ADDM) to fetch data directly from SGA for analysis

by running ADDM to fetch information from the latest Automatic Workload Repository (AWR) snapshots

by using Active Session History (ASH) data and performing hang analysis

by running ADDM in diagnostic mode

The valid time columns employee_time_start and employee_time_end are automatically created.

Thesamestatementmayfilteronbothtransactiontimeandvalidtemporaltimebyusingthe AS OF TIMESTAMP and PERIOD FOR clauses.

The valid time columns are not populated by the Oracle Server automatically.

The valid time columns are visible by default when the table is described.

Setting the session valid time using DBMS_FLASHBACK_ARCHIVE.ENABLE_AT_VALID_TIME sets the visibility for data manipulation language (DML), data definition language (DDL), and queries performed by the session.

mounting disk groups

acting as an I/O server to read data file blocks from ASM disks on behalf of database server processes

managing extent allocation for Oracle database segments

managing Allocation Units (AUs) for disk group content

managing space allocation for Oracle ASM files

acting as an I/O server to write data file blocks to ASM disks on behalf of Database Writer processes (DBWn)

The root password cannot be specified in a response file.

The sudo password must be specified in a response file.

orainstRoot.sh can be executed automatically by the Database installer by using sudo or root credentials.

root.sh can be executed automatically by the Database installer only if it is provided with root credentials.

root.sh can be executed automatically by the Database installer only by using sudo credentials.

The target database control file is synchronized from the recovery catalog with a partial resync at the next backup.

The recovery catalog is synchronized from the target database control file with a full resync at the next backup.

The target database control file is synchronized from the recovery catalog with a full resync at the next backup.

The recovery catalog is synchronized from the target database control file with a partial resync at the next backup.

Increase the size of tape I/O buffers.

Disable FORCE LOGGING for the database.

Increase the size of the database buffer cache.

Enable asynchronous disk I/O.

Increase the level of RMAN multiplexing.

It requires Oracle ASMLib to manage Automatic Storage Management (ASM) disks.

It creates one disk group during installation.

It includes both Oracle Restart and Oracle Automatic Storage Management (ASM) software.

Automatic Storage Management (ASM) requires that O/S groups OSASM and OSDBA be assigned as secondary groups for its installation owner.

It requires Oracle ASM Fitter Driver (ASMFD) to manage Automatic Storage Management (ASM) disks.

It requires the operating system ORACLE_BASE environment variable to be predefined before installation.

PDB2 will be opened READ WRITE.

PDB1 will be opened READ WRITE.

PDB1 will be MOUNTED.

PDB$SEED will be opened READ ONLY.

PDB$SEED will be MOUNTED

PDB2 will be MOUNTED.

All the triggers associated with the table are flashed back but are disabled.

Materialized views that use the CUSTOMERS table are flashed back.

LOB segments associated with the CUSTOMERS table are flashed back.

All the constraints defined on the table, except the referential integrity constraints, are flashed back.

Only the primary key constraint created for the table is flashed back, whereas all other indexes must be retrieved separately.

Fast Recovery Area must be enabled for the database

The EXECUTE privilege must be granted to a user on the DBMS_FLASHBACK package.

Undo retention guarantee must be configured for the database.

A supplemental log must be enabled for the primary key.

A supplemental log must be enabled for the primary key.

poorly trained users who do not commit transactions

the number of tablespaces containing tables updated by a transaction

issuing multiple savepoints during a transaction

the number of data files containing extents belonging to tables updated by a transaction

poorly written SQL

Tracking the most recent read time for a table segment in a user tablespace

Tracking the most recent write time for a table segment in a user tablespace

Tracking insert time by row for table rows

Tracking the most recent write time for a table block

Tracking the most recent read time for a table segment in the SYSTEM tablespace

Tracking the most recent write time for a table segment in the SYSAUX tablespace Correct

It can be used to patch existing Oracle software installations.

It can be used only on nodes with Oracle Grid Infrastructure installed.

It can be used to create a single-instance Oracle Database in an already-installed Oracle home. D)It can be used to deploy new homes without disrupting active databases.

It can be used to create templates of Oracle homes as gold images of only Oracle databases.

It can be used to upgrade only single-instance databases running on Oracle Restart.

The root and the seed database in the container database (CDB) are also duplicated.

A backup of PDB1 and PDB5 must exist before executing the command.

The SPFILE is copied along with the data files of the pluggable databases (PDBs).

An auxiliary instance must be started with the initialization parameter ENABLE_PLUGGABLE_DATABASE set to TRUE. E) The DUPLICATE command first creates a backup, and then duplicates the

PDBs by using the backup.

It is used to change failure priority only for HIGH or LOW priorities.

It is used to execute the advised repair script.

It is used to change failure priority only for the CRITICAL priority.

It is used to explicitly close the open failures.

It is used to inform the database about the repair after the repair script executes.

the Optimal Flexible Architecture (OFA) compliant path to store Oracle software and configuration files.

the location of Oracle Net Services configuration files

the list of a disk group names to be mounted by an Oracle Automatic Storage Management (ASM) instance at startup

default directories for temporary files used by temporary tablespaces

the temporary disk space used by Oracle Installer during installation

the maximum number of database files that can be opened by a database instance

Duplication can be done by having the auxiliary database instance pull backup sets from the target database instance.

A connection to an auxiliary instance is always required.

A subset of the target database can be duplicated.

A new DBID is always created for the duplicated database.

A connection to the recovery catalog instance is always required.

A backup of the target database is always required.

Duplication can be done by having the target database instance push copies to the auxiliary database instance.

Any Recovery Manager (RMAN) recovery catalog must be upgraded manually.

After a manual upgrade, TNSNAMES.ORA entries must be updated to reflect the new ORACLE_HOME.

Time zone files must be upgraded manually using the DBMS_DST PL/SQL package.

The new extended data type capability must be enabled by running the utlrp.sql script

The Oracle Application Express configuration should be updated after upgrading Oracle Database.

Application-common Transparent Security Data Protection (TSDP) policies can be created only if all the PDBs in the application container are closed.

Application-common TSDP policies are always container specific.

Application-common OLS policies can be created only if all the PDBs in the application container are closed.

Unified auditing can be automatically synchronized to all application PDBs in an application container.

Fine-grained auditing (FGA) policies in an application root are automatically synchronized to all application PDBs contained in the application container when they are updated.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to CDB$ROOT gathers object statistics only in PDB$SEED.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to CDB$ROOT gathers object statistics only in CDB$ROOT.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to CDB$ROOT gathers object statistics in all open pluggable databases (PDBs).

System statistics can be gathered only while the CDB is in MOUNT state.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to a PDB opened in read/ write mode gathers object statistics for that PDB.

It does not require the setup wizard.

It can be used to install and upgrade Oracle Database for single-instance and cluster configurations.

It can be used for both Oracle Database and Oracle Grid Infrastructure installation.

It uses a single RPM that automatically extracts and installs the Oracle Database software.

It can only install and configure Oracle Database software. The database has to be created separately.

It succeed

It fails because no parallel channels are allocated for the auxiliary databa

It fails because connection to the AUXILIARY instance must be as SYSD

Itsucceeds only if the target database is greater than 40

No catalogued backup of the TARGET is used to duplicate the databa

They can be retained forever.

They are always created automatically.

They are always created manually.

They are generated if STATISTICS LEVEL is set to TYPICAL.

They are generated if STATISTICS LEVEL is set to BASIC.

They are generated if STATISTICS LEVEL is set to ALL.

FLASHBACK DATABASE

FLASHBACK TABLE

FLASHBACK VERSION QUERY

FLASHBACK DATA ARCHIVE

FLASHBACK TRANSACTION

Media Management messages for SBT devices are always written to sbtio.log.

RMAN error stacks should be read from the bottom up as that is the order in which errors are generated.

RMAN error stacks should be read from the top down as that is the order in which errors are generated.

The RMAN LOG command line clause causes output issued during RMAN command compilation to be written to a log file and to standard output.

The RMAN LOG command line clause causes output issued during RMAN command compilation to be written to a log file only.

Media Management messages for SBT devices are written to an Oracle trace file.

he SPFILE is copied along with the datafiles of the pluggable databases (PDBs). The root and the seed database in the container database (CDB) are also duplicated.

A backup of pdb1 and pdb5 must exist before executing the command.

The duplicate command first creates a backup, and then duplicates the PDBs by using the backup.

A backup of CDB and pdb1 and pdb5 must exist before executing the command.

An auxiliary instance must be started with the initialization parameter ENABLE_PLUGGABLE_DATABASE set to TRUE.

to generate an XML metadata file that describes a non-CDB Oracle 12c database so that it can be plugged in as a PDB

to generate an XML metadata file from any unplugged PDB

to determine whether an XML file describes a PDB that can be plugged into the CDB in which you run the procedure

to generate a . pdb archive file for any PDB in the current CDB

to generate an XML metadata file that describes the current plugged-in PDB

A backup piece can belong to only one backup set.

A data file can be split into multiple sections stored in different backup sets.

A data file can be split into multiple sections stored in different backup pieces in the same backup set.

Blocks from multiple data files can be contained in one backup piece,

A backup set can contain only one backup piece.

A backup set must be written to media.

A backup set must be written to disk.

It is enabled for all users having SELECT privilege on SH.SALES.

Only successful queries of SH.SALES are written to the audit trail.

It is only enabled for user SH.

Audit records are always stored in an external audit file.

orainstRoot.sh can be executed automatically by the Database installer by using sudo or root credentials.

root.sh can be executed automatically by the Database Installer only if it is provided with root credentials.

The sudo password can be specified in a response file.

root.sh can be executed automatically by the Database installer only by using sudo credentials.

The sudo password must be specified in a response file.

The root password cannot be specified in a response file.

backup retention policy

default backup device type

default section size for backups

default destinations for backups

multiple backup device types for a single backup

All historical data older than two years, if any, is purged from the flashback archive FDA1.

An error is returned because the retention period cannot be reduced.

All the flashback data archives are purged and the subsequently created flashback archives are maintained for two years

All historical data older than two years, if any, is archived to flashback logs and the flashback archive is set to new retention time.

Space might be reclaimed proactively before space pressure occurs.

Space is always reclaimed proactively before space pressure occurs.

Space might be reclaimed automatically when the retention period for Flashback logs is lowered.

Space is always reclaimed automatically when the retention period for Flashback logs is lowered.

Space is only reclaimed when there is space pressure in the Fast Recovery Area (FRA).

Pre-existing backups of the database to be duplicated are required for the "push" method of duplication.

Pre-existing backups of the database to be duplicated are required for the "pull" method of duplication.

Pre-existing backups of the database to be duplicated are always used if they exist.

Image copies can be used to duplicate the active database.

The active database must be duplicated while in OPEN state.

No connection to the recovery catalog is required for active database duplication.

Backup sets can be used to duplicate the active database.

Data file 24 can be recovered only while connected to PDB2.

Data file 24 can be restored and recovered while connected to CDB$ROOT.

Data file 24 can be restored only while connected to CDB$ROOT.

Data file 24 can be restored only while connected to PDB2.

Data file 24 can be recovered while connected to PDB2.

Data file 24 can be recovered while connected to CDB$ROOT.

using Database Replay

using SQL Developer

using Oracle Data Pump

using operating system file copy utilities

using Database Upgrade Assistant

using the CREATE TABLE AS SELECT SQL statement

Application PDBsthat are subsequently created in the APP1 application container will be cloned from APP1$SEED.

An application seed PDB is created for APP1.

An application root PDB is created for APP1.

A default service is created for the application root APP1.

Application PDBs that are subsequently created in the APP1 application container will be cloned from PDB$SEED.

APP1 can never be unplugged.

The ORCL database, the Oracle ASM instances, the +DATA and +FRA disk groups, and the LISTENER are started.

Only the ORCL database instance is started.

Only the ORCL database and the ASM instances are started.

Only the ORCL database instance, the Oracle ASM instance, and the +DATA and +FRA disk groups are started.

Only the ORCL database instance and the +DATA and +FRA disk groups are started.

CDB2 must be in shared UNDO mode only.

CDB2 must be in archivelog mode.

CDB1 must be in archivelog mode.

CDB1 and CDB2 must both be in local UNDO mode.

CDB1 must be in shared UNDO mode only.A container database, CDB1, contains a pluggable database PDB1.

CDB1 and CDB2 must be in shared UNDO mode.

The database must have FLASHBACK DATABASE ON to perform Database Point-in-Time Recovery.

The database must be in MOUNT state when performing Database Point-in-Time Recovery.

Database Point-in-Time Recovery is performed by the Managed Recovery Process (MRP)

The Database must be in ARCHIVE LOG mode.

The target point for the recovery must be specified as a stime or System Change Number (SCN).

The database must be open RESETLOGS after Database Point-in-Time Recovery.

FLASHBACK transaction query requires undo to retrieve all versions of a row that existed between two points in time.

FLASHBACK drop requires that the RECYCLEBIN parameter be set to ON.

FLASHBACK version query requires that the RECYCLEBIN parameter be set to ON.

FLASHBACK DATA ARCHIVE requires undo to store all versions of all rows of a table being tracked.

FLASHBACK drop requires undo to retrieve all versions of a row that existed two points in time.

FLASHBACK version query requires undo to retrieve all versions of a row that existed between two points in time.

By default it analyzes a period of time corresponding to the last 4 hours of activity.

When ADDM reports multiple findings, summing all their impacts can yield to more than 100% of DB time

By default it analyzes a period of time corresponding to the last 24 hours of activity.

It runs automatically after each AWR snapshot.

Results are written to the alert log.

CDB1 and CDB2 must be in shared undo mode.

A common user must exist in CDB2 with the CREATE PLUGGABLE DATABASE privilege.

All transactions in HR_PDB1 of CDB1 must commit before the cloning process starts.

Cloning HR_ROOT automatically clones HR_PDB1.

The HR_PDB1clone created in CDB2 will be in mount state when cloning ends.

V$SESSION_EVENT

V$SESSTAT

V$SESSION_WAIT

V$SESSION_WAIT_CLASS

V$SESSION

cloning a remote container database in interactive mode

cloning a remote pluggable database in silent mode

relocating a remote pluggable database in interactive mode

relocating a remote container database in silent mode

cloning a remote container database in silent mode

relocating a remote pluggable database in silent mode

relocating a remote container database in interactive mode.

All metrics are instance related.

Cleared stateful alerts are displayed by querying DBA_ALERT_HISTORY.

A space usage management alert is automatically cleared after the underlying problem is resolved

They are generated by SMON when a tablespace is 97% full.

Metrics are statistical counts for a specific unit.

STATISTICS_LEVEL must be set to ALL to generate alerts.

It can only be launched from the command line interface.

It can be launched from both the command line and the Universal Installer (OUI) interfaces.

It can be used to create container databases and non-container databases.

It can be used to change the character set of an existing database.

It can be used to convert a non-container database to a container database.

Assign the appropriate operating system groups to SYSBACKUP, SYSDG, SYSKM.

Grant SYSBACKUP, SYSDG, and SYSKM privileges to the intended users.

Re-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege and the FORCE argument set to No.

Re-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege, and FORCE arguments set to Yes.

Re-createthepasswordfileintheOracleDatabase12cformat. Correct

DataisredactedfortheEMP.SALcolumnonlyiftheSCOTTsessiondoesnothavetheMGR role set.

DataisredactedforEMP.SALcolumnonlyiftheSCOTTsessionhastheMGRroleset.

Data is never redacted for the EMP_VW.SAL column.

Data is redacted for the EMP_V.SAL column only if the SCOTT session has the MGR role set.

Data is redacted for the EMP_V.SAL column only if the SCOTT session does not have the MGR role set. Correct

The password for the encryption must be set up.

Oracle wallet for the encryption must be set up.

All the tablespaces in the database must be encrypted

Oracle Database Vault must be enabled.

A PDB snapshot is always a full copy of the source PDB.

A PDB snapshot is always a sparse copy of the source PDB.

A snapshot copy PDB depends on a storage snapshot which can only be stored on specific file systems.

A PDB snapshot depends on a storage snapshot which can be stored on any file system.

A PDB snapshot depends on a storage snapshot which can only be stored on specific file systems.

A snapshot copy PDB depends on a storage snapshot which can be stored on any file system.

A snapshot copy PDB can be created from a stand-alone clone PDB.

OSASM

OSRACDBA

OSKMDBA

OSDBA

E）OSOPER

Compare Period ADDM report

AWR Compare Period report

Active Session History (ASH) report

Taking a new snapshot and comparing it with a preserved snapshot.

RESYNC CATALOG

CROSSCHECK BACKUP OF ARCHIVELOG ALL

LIST ARCHIVELOG ALL

LIST EXPIRED

LIST ARCHIVELOG

REPORT OBSOLETE

It analyzes a period of time corresponding to the 12 hours of activity.

It runs automatically after each AWR snapshot.

A DBA can run it manually.

Results are written to the alert log.

It analyzes a period of time corresponding to the last day of activity.

A target database’s persistent RMAN configuration settings are always stored in the target’s control file

Backup older than the recovery window retention policy are always deleted automatically if the backup location has insufficient space.

Backups written to the fast recovery area (FRA) that are oboslete based on the redundancy retention policy can be deleted automatically to free space.

The RMAN SHOW ALL command displays only settings with nondefault values.

A target database’s persistent RMAN configuration settings are always synchronized automatically with the RMAN catalog.

The V$RMAN_CONFIGURATION view displays only settings with valuesthat have been modified. G)A DBA must specify either a redundancy retention policy or a recovery window retention policy.

SBT tape compression can be used even if no RMAN compression is configured.

Any backup set written to the SBT device in this configuration can contain a maximum of two backup pieces.

Any backup written to the SBT device in this configuration can contain a maximum of two backup sets.

SBT tape compression and RMAN backup compression should be used in parallel.

The SBT device should be configured to use PARALLELISM 2 to allow both tape drive to be used simultaneously.

user-managed backups of data files and control files

flashback logs

RMAN backups that are obsolete

archived redo log files that have multiple copies in a different archive location

Automatic conversion of endianess occurs.

The source and target platforms must have the same endianess.

The source PDB can be in MOUNT or OPEN state.

The source PDB must not be an application root.

The source PDB must be in MOUNT state.

A backup of the PDB must exist, taken using the BACKUP command with the To PLATFORM clause.

Flashback logs are written sequentially, and are archived.

Flashback Database uses a restored control file to recover a database.

The Oracle database automatically creates, deletes, and resides flashback logs in the Fast Recovery Area.

Flashback Database can recover a database to the state that it was in before a reset logs operation.

Flashback Database can recover a data file that was dropped during the span of time of the flashback.

Flashback logs are used to restore to the blocks' before images, and then the redo data may be used to roll forward to the desired flashback time.

1,3,5, 6, 9

1,3, 5, 7, 10

1,2, 5, 7,4, 10

1,3, 5, 6, 10

1,3,5, 6, 10

1,3,5,8, 6, 10