1z0-083 Oracle Database Administration II Questions and Answers

It performs a shutdown and then a restart of all processes in both Oracle Grid Infrastructure and Oracle Database home during the patching process.

It must be invoked by a user with root user privileges.

Patches are applied via opatchauto.

Users must always input patch plans to opatchauto.

It requires the Oracle Grid Infrastructure and Oracle Database instances to be shut down before being invoked.

It applies patches in nonrolling mode by default.

It is used to apply interim patches to Oracle Grid Infrastructure and Oracle Database home combinations.

A direct upgrade can be performed only from the immediately preceding Oracle Grid Infrastructure version.

The newer version is installed in a separate Oracle Grid Infrastructure home on the same server as the existing version.

An existing Oracle base can be used.

The upgrade process will automatically install all mandatory patches for the current version of Oracle Grid Infrastructure.

Existing Oracle Database instances must be shut down before starting the upgrade.

Only the grid user can perform the upgrade.

The UNDO TABLESPACE clause is always required when no connection exists to the recovery catalog and the TARGET database is closed.

RMAN disk-based backups of the database to be duplicated can be used by the auxiliary instance.

The UNDO TABLESPACE clause is always required when no connection exists to the TARGET instance.

The UNDO TABLESPACE clause is never required.

RMAN "pushes" the backups of the database to be duplicated over the network to the auxiliary instance.

Enable Memory Access Mode, which reads performance data from SGA.

Use emergency monitoring to fetch data directly from SGA for analysis.

Run Automatic Database Diagnostic Monitor (ADDM) to fetch information from the latest Automatic Workload Repository (AWR) snapshots.

Use Active Session History (ASH) data and hang analysis in regular performance monitoring,

Run ADDM in diagnostic mode.

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.

after losing a SYSAUX tablespace data file

after losing all members of an INACTIVE online redo log group

after losing all members of the CURRENT online redo log group

after losing all copies of the control file

after losing an UNDO tablespace that is in use

A non-CDB can be cloned into a PDB.

A user with SYSDBA or SYSBKUP must be logged in with RMAN to CDB$ROOT when cloning a PDB.

Only one PDB can be cloned at a time.

Two or more PDBs can be cloned with the same command.

A user with SYSDBA or SYSBKUP must be logged in with RMAN to the non-CDB being cloned when cloning a non-CDB.

The target and auxiliary instance passwords must be the same.

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.

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.

It recompiles all stored PL/SQL code by using utlrp.sql.

It empties the RECYCLE BIN.

It performs prerequisite checks to verify if the Oracle database is ready for upgrade.

It sets all user tablespaces to “read-only” before starting the upgrade.

It removes the AUDSYS schema and the AUDIT_ADMIN and AUDIT_VIEWER roles

It increases tablespace size, if required, to meet upgrade requirements.

It succeeds.

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

It fails because connection to the AUXILIARY instance must be as SYSDBA.

Itsucceeds only if the target database is greater than 400M.

No catalogued backup of the TARGET is used to duplicate the database.

Flashback logs are automatically purged when DB_FLASHBACK_RETENTION_TARGET is set lower than the time they have already been retained.

Flashback logs are monitored and proactively deleted when beyond the retention period defined in DB_FLASHBACK_RETENTION_TARGET only after there is space pressure.

Flashback logs are monitored and proactively deleted when beyond the retention period defined in DB_FLASHBACK_RETENTION_TARGET before there is space pressure.

Flashback logs are monitored for being older than the retention period defined in DB_FLASHBACK_RETENTION_TARGET and can be deleted by an administrator written event trigger.

Flashback logs are automatically purged whenever the value of DB_FLASHBACK_RETENTION_TARGET is changed.

They are generated if STATISTICS_LEVEL is set to TYPICAL.

They are always created manually.

They are always created automatically.

They are generated if STATISTICS_LEVEL is set to BASIC.

They are generated if STATISTICS_LEVEL is set to ALL.

They can be retained forever.

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.

The control file is backed up whenever a new tablespace is created.

The server parameter file (SPFILE) is automatically backed up each time the control file is backed up.

The control file is backed up whenever a new table is created.

The control file is backed up whenever an RMAN backup is successfully recorded in the catalog.

It requires the use of fast recovery area (FRA).

The control file is backed up automatically each time the SPFILE is backed up manually.

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.

Tables or table partitions can be recovered by using an auxiliary instance only.

Tables or table partitions with a foreign key cannot be recovered.

Tables or table partitions can be recovered only when the database is in mount state.

Tables or table partitions from the system and sysaux tablespaces cannot be recovered.

Tables with not null constraints cannot be recovered.

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.

SGA_MIN_SIZE cannot be set for a PDB.

Setting SHARED_POOL_SIZE for a PDB guarantees a minimum amount of Shared Pool memory for that PDB.

Setting SGA_TARGET for a PDB guarantees a minimum amount of SGA memory for that PDB.

The SHARED_POOL_SIZE setting for a PDB can be up to 80% of the SHARED_POOL_SIZE setting of the root container.

Setting DB_CACHE_SIZE for a PDB guarantees a minimum amount of Database Buffer Cache memory for that PDB.

The SGA_TARGET setting for a PDB cannot exceed 50% of the SGA_TARGET value of the root container.

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 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.

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.

All archive redo log files are automatically copied to the duplicate database.

The duplicate database has the same directory structure as the source database.

The duplicate database is created by using the backups created during the execution of

he duplicate command.

The password file and SPFILE for the duplicate database dup1 are created in their respective default locations.

The duplicate database is created without using RMAN backups and prod1 is allowed to remain open during duplication.

when control file metadata for archive log backups or image copies has been overwritten in the target database's control file due to being older than CONTROL_FILE_RECORD_KEEP_TIME

when a new tablespace is added to a registered target database

when a backup of the current control file is created

when control file metadata for data file backups or image copies has been overwritten in the target database's control file due to being older than CONTROL_FILE_RECORD_KEEP_TIME

when the target is first registered

Run the SQL Access Advisor.

Run the Memory Advisor for the shared pool.

Run the SQL Tunning Advisor.

Run the Memory Advisor for the Program Global Area.

Run the Memory Advisor for the System Global Area.

A proxy PDB must exist in the application root in the local CDB.

PDB3's application root replica must exist in the local CDB.

The HR_ROOT replica must exist in the remote CDB.

A database link must exist in the remote CDB referring to the local CDB.

A proxy PDB must exist in the application root in the remote CDB.

A database link must exist in the local CDB root referring to the remoteCDB.

A lost PFILE can be re-created from alert.log using SQL*PLUS.

A lost index tablespace can be re-created without performing any recovery.

A lost password file can be manually re-created with the orapwd utility.

A lost password file can be re-created with SQL*PLUS.

A lost SPFILE can be recovered from memory using SQL*PLUS.

A lost TEMPFILE must always be re-created manually.

The inserts on USER1.EMP remain uncommitted when the session connected to PDB2.

The inserts on USER1.EMP were committed when the session inserted a row into USER2. DEPT.

The insert on USER2.DEPT fails because of the active transaction in the parent container.

The insert on USER2.DEPT is a recursive autonomous transaction by the child session and is committed.

The inserts on USER1.EMP were rolled back when the session connected to PDB2

The insert on USER2.DEPT is uncommitted.

The inserts on USER1.EMP were committed when the session connected to PDB2.

Backing up a database in NOARCHIVELOG mode using O/S utilities requires that the database instance be started and the databased be in the MOUNT state.

Backing up a database in ARCHIVE LOG mode using O/S utilities requires that the database instance be started and the database be in MOUNT state.

An Oracle database can be restored from backup files copied using O/S utilities.

Oracle data file backups, copied using an O/S utility, can be added to the RMAN catalog as IMAGE COPIES.

Backing up a database in NOARCHIVELOG mode using O/S utilities requires that the database instance be shut down.

Oracle archive log backups, copied using an O/S utility, can be added to the RMAN catalog as a backup set.

Backing up a database in ARCHIVE LOG mode using O/S utilities requires that the database instance be started and the database be in OPEN state.

Compare Period ADDM report

AWR Compare Period report

Active Session History (ASH) report

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

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 Oracle Database time model should be used to find the database and instance areas most in need of tuning.

Tuning activities should stop once the user is satisfied with performance.

Tuning activities should stop once agreed service levels for performance have been met.

The database instance memory should always be tuned before tuning any file systems.

SQL statements should always be tuned before tuning any file systems.

The alert log should be used to find the database and instance areas most in need of tuning.

Tune individual SQL statements using the SQL Tuning Advisor.

Identify poorly tuned SQL statements using Automatic Database Diagnostic Monitor.

Test the application as a whole using tuned SQL statements.

Test tuned SQL statements one at a time for all statements in the application.

Identify poorly tuned SQL statements using the SQL Tuning Advisor.

Tune SQL statements as a group using the SQL Tuning and SQL Access Advisors.

Tablespaces are automatically created as need while importing full exports in either a non-CDB or a PDB.

Oracle attempts to convert conventional database users to local users when moving schemas from a non-CDB to a PDB.

A new PDB is automatically created when importing a non-CDB into a CDB.

Oracle attempts to convert common users to conventional users when moving schemas from a PDB to a non-CDB.

Moving data from a PDB to a non-CDB is only possible by using transportable tablespace export and import.

Moving data from a non-CDB to a PDB is only possible by using conventional export and import.

1,3,6

1,2,5

3,4,5

2,3,5,6

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.

FLASHBACK QUERY can retrieve REDO records from ONLINE and ARCHIVE D REDO LOG files.

FLASHBACK VERSION QUERY can retrieve REDO records from ONLINE and ARCHIVE D REDO LOG files.

FLASHBACK TABLE can undrop a column.

FLASHBACK DROP can undrop an index when undropping a table.

After a database is restored from flashback logs using the FLASHBACK DATABASE command, it is sometimes rolled forward using redo logs.

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.

after losing all members of the CURRENT online redo log group

after losing all copies of the control file

after losing an UNDO tablespace that is in use

after losing all members of an INACTIVE online redo log group

after losing a SYSAUX tablespace data file

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

by using the RMAN switch command to set the new location for the data files

by using the RMAN duplicate command with nofilenamecheck to recover the database to the new host

by using the RMAN duplicate command with dbid and set new name for tablespace to recover the database to the new host

by creating a new database in the new host, and then using the RMAN recover command

Compressed backups cannot have a section size defined.

Compressed backups can be written only to media.

Binary compression adds CPU overhead to backup operations.

Unused blocks below the high water mark are backed up.

Compression can be done only for locally managed tablespaces.

Create SQL plan directives for each of the regressed statements.

Use The SQL Tuning Advisor for each of the regressed statements.

Create an adaptive execution plan for each of the regressed statements

Use the SQL Access Advisor for each of the regressed statements.

It cannot be backed up manually as a binary copy.

It gets backed up automatically by RMAN as a trace file containing SQL statements for control file re¬creation when a database backup occurs.

It can be backed up manually as a binary copy.

It can get backed up automatically as a binary copy.

It gets backed up automatically by RMAN when the BACKUP SPFILE command is used.

It can be backed up manually as a trace file containing SQL statements for control file recreation.

all backups prior to 10th of August

all backups prior to 22nd of August

all backups prior to 20th of August

all backups prior to 24th of August

all backups prior to 17th of August

Backups must be done incrementally.

Backups must be contained in backup sets.

Backups can be taken only if the database is in ARCHIVE LOG mode.

Backups can be done incrementally.

The database must be registered in an RMAN catalog.

Only consistent backups can be created.

Backups can be taken only if a fast recovery area is configured.

Backups can be written only to disk.

Backups can be taken only for data files.

Binary compression cannot be applied to the backup.

Backups can be written only if checksums are stored for each block.

Backups can be written only to media.

when any archived log from, before, or after the most recent backup is corrupt.

after losing all copies of the control file

after losing an archived log from after the most recent backup

after losing an archived log from before the most recent backup

after losing the SYSTEM tablespace

It can be used to transport data from a non-CDB to a PDB.

It can be used to clone a CDB.

It can be used to transport data between PDBs.

It can be used to transport data from a PDB to a non-CDB.

It can be used to create a new PDB.

The response file can specify the path of the sudo program.

The response file must contain the root or sudo password.

Silent install always runs operating scripts automatically.

The response file can specify the root or sudo password.

The installer will prompt for the root or sudo password.

They must be written to media.

They can be written only to disk.

They can be created only by using the COPIES option of a BACKUP command.

They can be created by using the RMAN CONFIGURE command to specify duplexing before taking a backup.

They can be written to media.

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

The Transparent Data Encryption (TDE) keystore is backed up using RMAN.

Vendor-specific media management software can be used for making encrypted RMAN backups to media.

The BACKUP BACKUPSET command can encrypt and decrypt backup sets.

Image copies can be encrypted.

Keystore-based encryption is the default mode for RMAN backup encryption.

Backup encryption can be enabled selectively for specific tablespaces.

The General Purpose of Transaction Processing templates are most suitable when concurrency and recoverability are key criteria.

Oracle DBCA templates can store only logical structure and not database files.

New templates can only be created by modifying an existing user-created template.

The Data Warehouse template is most suitable when transaction response time is the key criterion.

Oracle DBCA templates can be used to create new databases and duplicate existing databases.

1,2,4,5,7,8

1,2,4,6,7,8

1,2,3,4,5,7,8

1,2,3,4,5,6,7,8

2,4,5,6,7

when the duplicate ... from active database command contains the section size clause

when you perform active database duplication on a database with flashback disabled

when you specify set encryption before the duplicate ... from active database command

when the number of auxiliary channels allocated is equal to or greater than the number of target channels

when you perform active database duplication on a database that has readonly tablespaces

It considers the filters in WHERE clauses when generating execution plans for SQL statements.

It obeys all hints.

It considers object statistics when generating execution plans for SQL statements.

It updates stale object statistics in the Data Dictionary.

It can only use SQL Plan Directives tied to the SQL statement for which a plan is being generated.

It can re-optimize execution plans after previous executions detect suboptimal plans.

CDB1, PDB$SEED, PDB1, and PDB2

PDB$SEED, PDB1, and PDB2 only

CDB1 and PDB$SEED only

CDB1, PDB1, and PDB2 only

CDB1, PDB$SEED, and PDB1 only

A backup set may be duplexed with both copies written to disk.

An image copy on disk can be copied to disk.

A backup set may be duplexed with both copies written to sbt.

A backup set may be duplexed so that one copy is written to sbt and the other to disk.

An image copy on disk can be copied to sbt.

An image copy on sbt can be copied to disk.

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

OSASM

OSRACDBA

OSKMDBA

OSDBA

E）OSOPER

If no PDB plan is enabled for a pluggable database, then all sessions for that PDB are treated to an equal degree of the resource share of that PDB.

In a PDB plan, subplans may be used with up to eight consumer groups.

If a PDB plan is enabled for a pluggable database, then resources are allocated to consumer groups across all PDBs in the CDB.

If no PDB plan is enabled for a pluggable database, then the PDB share in the CDB plan is dynamically calculated.

If a PDB plan is enabled for a pluggable database, then resources are allocated to consumer groups based on the shares provided to the PDB in the CDB plan and the shares provided to the consumer groups in the PDB plan.

It is only possible for RMAN to connect to a pluggable database as a target if an RMAN Virtual Private Catalog is used.

It is always possible for RMAN to connect to a pluggable database as a target if any RMAN Catalog is used.

A Virtual Private Catalog used to register a container database must be created in a pluggable database.

A Virtual Private Catalog used to register a container database can be created in a pluggable database.

It is always possible for RMAN to connect to a pluggable database as a target.

A Virtual Private Catalog used to register a container database can be created in a non-container database.

It is automatically synchronized with its application root PDB when an application is upgraded. B)It cannot be added to an application container after the application container has already been created.

A new application PDB created by cloning an application seed PDB can have an old version of the application installed after cloning completes.

It is automatically synchronized with its application root PDB when an application is installed.

It cannot be dropped from its application container.

A new application PDB created by cloning an application seed PDB can have an up-to-date version of the application installed after cloning completes.

It is not required in an application container.

If a row lock is held by a nonexistent transaction, the block containing the row is media corrupt.

DB_BLOCK_CHECKING=TRUE causes a check sum to be added to each data block to help detect physical or media corruption.

A media corrupt block is one where the block is not formatted correctly.

The ANALYZE TABLE VALIDATE STRUCTURE CASCADE command verifies that each table row has an index entry pointing to it.

If a row lock is held by a nonexistent transaction, the block containing the row is logically corrupt.

DB_LOST_WRITE_PROTECT=TYPICAL causes extra logging overhead on the standby database.

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.

1,3,5,7

2,5,6

1,5,6

3,4,1.6,8

1,3,5,6,7

The REVENUE table must be a list-partitioned table.

The CONTAINERS clause cannot be used in queries on the REVENUE table.

The REVENUE table partitions are not pruned across the PDBs automatically.

The REVENUE table must be a composite-partitioned table.

The MAPTABLE table defines a logical partition key on a commonly used column for the REVENUE table.

With Automatic Shared Memory Management, the database instance can increase the Large Pool size by reducing the Shared Pool size.

With Automatic Memory Management, the database instance can increase the System Global Area size by reducing the Program Global Area size.

Automatically tuned and resized System Global Area components will always revert to their initial sizes after an instance restart.

Automatic Memory Management must be used together with locking the System Global Area into physical memory.

With Automatic Shared Memory Management, the database instance can increase the Program Global Area size by reducing the System Global Area size.

On Line Transaction Processing systems often use less Program Global Area than Decision Support Systems.

They can view data from any data dictionary view or dynamic performance view.

They can drop any tablespace.

They can view data from any user-defined tables.

They can create any table.

They cannot create restore points.

They cannot drop tablespaces.

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.

ADDM can recommend shrinking the buffer cache.

ADDM can recommend extending the buffer cache.

By default, MMON creates an AWR snapshot every 30 minutes.

ADDM performs its analysis only when a DBA requests it.

By default, AWR snapshots are automatically purged after eight days.

AWR snapshots must be deleted when no longer required by ADDM.

RMAN must be connected to the target database instance and the auxiliary instance.

A most recent backup set of the PROD database must exist.

Flashback must be enabled for the PROD database.

The target database must be in MOUNT state.

It is enabled by performing a software-only Oracle Database installation and then running the roohctl ¬enable script.

It requires the Rapid Home Provisioning service.

Its configuration data and log files reside in subdirectories under the Oracle home.

It is enabled by performing an Oracle Database installation with database creation and then running the roohctl -enable script.

It contains an image that can be distributed across multiple servers.

The base catalog owner must give the Virtual Private Catalog access to metadata for one or more PDBs.

The target PDB must be registered in both the base catalog and the Virtual Private Catalog.

The base catalog must be used by RMAN when performing point-in-time recovery for the PDB registered in the Virtual Private Catalog.

The base catalog must be enabled for Virtual Private Catalog use.

The target PDB must be registered in a Virtual Private Catalog.

The target PDB must be registered in a base catalog.

Open the CDB instance in restricted mode. In CDB$ROOT, drop the UNDO tablespace. Execute ALTER DATABASE LOCAL UNDO ON in each PDB, and then restart the CDB instance.

Open the CDB instance in upgrade mode. In CDB$ROOT, execute ALTER DATABASE LOCAL UNDO ON, and then restart the CDB instance.

Open the CDB instance in upgrade mode. In each PDB, execute ALTER DATABASE LOCAL UNDO ON, create an UNDO tablespace, and then restart the CDB instance.

Open the CDB instance in restricted mode. In CDB$ROOT, execute ALTER DATABASE LOCAL UNDO ON. create an UNDO tablespace in each PDB, and then restart the CDB instance.

Open the CDB in read-only mode. In CDB$ROOT, execute ALTER DATABASE LOCAL UNDO ON, and then change the CDB to read/write mode.

They can only be written to disk.

They can be encrypted using Transparent Data Encryption (TDE).

They can be used as a level 0 incremental backup.

They can be used as a level 1 incremental backup.

They are the only backup option available for databases in NOARCHIVELOG mode.

Tablespaces from different PDBs with identical names must be backed up by connecting RMAN separately to each PDB to back up the tablespaces.

The BACKUP DATABASE command will create a pluggable database (PDB) backup when RMAN is connected to a PDB.

SPFILE backups can be created while connected to an application root PDB.

The BACKUP DATABASE PLUS ARCHIVE LOG command will back up archive logs when RMAN is connected to a PDB.

The BACKUP PLUGGABLE DATABASE command can be used to back up CDB$ROOT.

It can manage database resources on the server where it is installed or on a different server.

The CSS daemon runs from the Grid Infrastructure home.

It supports volume management, file system, and automatic restart capabilities.

It requires Oracle Automatic Storage Management (ASM) components to be installed separately.

It must be installed before the Oracle database software is installed.

connecting to the target database and a recovery catalog to execute the duplicate command

creating a password file for an auxiliary instance

connecting to an auxiliary instance

matching the database identifier (DBID) of the source database and the duplicate database

creating an SPFILE for the target database

A media manager always writes RMAN requested backups to tape.

A media manager is required to create RMAN image copies.

A media manager is required to create RMAN proxy copies.

The media manager layer (MML) routines provided by Oracle support any vendors' media management products.

By default, a request for a proxy copy may result in a backup set being created.

RMAN encryption keys are stored in a database keystore.

RMAN can encrypt the Oracle Database password file.

Dual-mode encrypted backups can be restored only if both the password and the keystore used for encryption are available.

The SET ENCRYPTION command overrides encryption settings specified by the CONFIGURE ENCRYPTION command.

Password encryption can be persistently configured using the CONFIGURE ENCRYPTION command.