1z0-083 Oracle Database Administration II Questions and Answers

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.

It is used in both clustered and non-clustered environments.

You can add and remove components from an Oracle Restart configuration with Server Control (SRVCTL) commands.

It runs from the Oracle Grid Infrastructure home.

If you shut down a database instance with SQL*Plus, Oracle Restart interprets this as a database failure and attempts to restart the instance.

The Server Control (SRVCTL) utility can be used to start and stop Oracle Restart.

It can manage Oracle Database instances, Oracle Net Listeners, and Oracle Automatic Storage Management instances.

RESYNC CATALOG

CROSSCHECK BACKUP OF ARCHIVELOG ALL

LIST ARCHIVELOG ALL

LIST EXPIRED

LIST ARCHIVELOG

REPORT OBSOLETE

Single-byte character sets provide better performance than multibyte character sets.

Unicode enables information from any language to be stored using a single character set.

Unicode is the only supported character set for Oracle databases created using Database Configuration Assistant (DBCA).

Single-byte character sets always use 7-bit encoding schemes.

Multibyte character sets allow more efficient space utilization than single byte character sets.

Single-byte character sets always use 8-bit encoding schemes.

2,4,5,6

1,2,3,4,5,6

1,2,4,5

2,4,5

1,3,4,5

DBUA must be launched from the target Oracle Home.

Multiple databases with the same ORACLE_HOME can be upgraded simultaneously.

A whole database backup must exist before upgrade.

The Pre-Upgrade Information Tool script is executed by DBUA.

All pluggable databases are automatically upgraded as part of a container database upgrade.

The database must be opened in read-only mode.

Re-create or migrate the password file to the Oracle Database 12c format

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

Copy the password file from a sample file in the DBS dierectory

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

By default, members of the OSASM group can access Automatic Storage Management and RDBMS instances.

The primary group for the Oracle Grid Infrastructure and Oracle Database owners must be the Oracle Inventory group.

The Oracle Grid Infrastructure installation must be owned by the grid user.

The Oracle Grid Infrastructure owner owns Oracle Restart and Oracle Automatic Storage Management binaries.

The Oracle Grid Infrastructure owner must have OSOPER, OSBACKUPDBA, and OSKMDBA as secondary groups.

The same OSDBA group must be used for Automatic Storage Management and the Oracle Database.

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 uses multisection backup.

It uses parallelization for the backup set.

It uses asynchronousI/O for the backup.

It creates compressed backup sets.

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.

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

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.

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

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.

RMAN can recover tables owned by the SYSTEM user.

RMAN can recover tables owned by the SYS user.

RMAN can recover tables in the SYSTEM tablespace.

RMAN always uses an auxiliary instance.

RMAN can recover a table after a DDL operation has altered the table structure.

RMAN can recover tables in the SYSAUX tablespace.

RMAN can recover tables in a standby database.

The target database must be open

The duplication process can use existing backup sets or image copies

The duplication process can use existing backup sets or image copies.

The target database must be in mount state.

The duplication -process pushes backup sets to the auxiliary instance.

The duplication process pushes image copies to the auxiliary instance.

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.

Data Pump full database export and import

cloning the non-CDB as a PDB

replication using GoldenGate

Data Pump transportable tablespaces

Data Pump full transportable database

the DBMS_PDB package

It is not possible if an archived log is missing.

It is performed automatically after the database is opened; however, blocks requiring recovery are not available until they are recovered.

Setting FAST_START_MTTR_TARGET to a lower value reduces instance recovery time by causing dirty buffers to be written to disk more frequently, thereby reducing the number of I/Os needed during instance recovery.

It is performed by the Recovery Writer (RVWR) background process.

Setting FAST_START_MTTR_TARGET to a higher value reduces instance recovery time by causing The log writer to write more frquently, thereby reducing the number of I/Os needed during instance recovery.

It is performed automatically while the database remains in MOUNT state. Then the database is opened.

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.

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.

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.

Data file 24 can be recovered while PDB2 is opened.

Data file 24 must be recovered while the CDB is opened.

Data file 24 can be recovered while CDB$ROOT and PDB$SEED are opened.

Data file 24 cannot be recovered while the CDB is opened.

Data file 24 must be recovered while PDB2 is closed.

DBMS_PDB.CHECK_PLUG_COMPATIBILITY can be run against a PDB archive.

They contain a PDB manifest file and all the data files in uncompressed form for a PDB.

They contain all the data files only in uncompressed form for a PDB.

They must be created using the DBMS_PDB package.

They contain a PDB manifest file and all the data files in compressed form for a PDB.

They contain all the data files only in compressed form for a PDB.

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.

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.

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.

FLASHBACK DATABASE

FLASHBACK TABLE

FLASHBACK VERSION QUERY

FLASHBACK DATA ARCHIVE

FLASHBACK TRANSACTION

FLASHBACK DATABASE only uses FLASHBACK LOGS to get the database to the desired flashback time.

It requires that the target database be in ARCHIVELOG mode.

FLASHBACK LOGS are archived after a log switch.

A database can be flashed back using SQL*PLUS.

It always generates REDO and UNDO.

Queries and DML have the same FLASHBACK LOG overhead when flashback is enabled for a database.

It can be performed using an auxiliary instance managed by RMAN.

It can be performed using an auxiliary instance managed by a DBA.

It can be used to recover a truncated table.

It can be performed repeatedly until the correct time is found without using an RMAN catalog. E)RMAN always includes tablespaces containing UNDO segments in the recovery set.

RMAN automatically adds any required tablespaces to the recovery set to make it selfcontained. G) FLASHBACK DATABASE must be enabled for it to work. H) It can be used to recover a dropped

tablespace.

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

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

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.

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.

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.

TheC# # B_ADMIN user can perform all back up and recovery operation susing RMAN only.

The C # # C_ADMIN user can perform the data guard operation with Data Guard Broker.

The C # # A_ADMIN user can perform wallet operations.

The C # # D_ADMIN user can perform backup and recovery operations for Automatic Storage Management (ASM).

The C # # B_ADMIN user can perform all backup and recovery operations using RMAN or SQL* Plus.

It fails because Data Pump cannot be container.

It creates a full export of the root

It creates a full export of the root

It creates a full export of only the used while connected to the root container and PDB1. container and all PDBs. container and all open PDBs. root container.

restore and recover database

flashback transaction

flashback database

flashback table and transaction

flashback table

OSASM

OSRACDBA

OSKMDBA

OSDBA

E）OSOPER

V$SESSION_EVENT

V$SESSTAT

V$SESSION_WAIT

V$SESSION_WAIT_CLASS

V$SESSION

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.

It requires Oracle ASMLib to manage Automatic Storage Managerment (ASMl) 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 ars groups OSASM and OSDBA be assigned assecondary groups for its installation owner.

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

It requires Oracle ASM Filter Drver (ASMFD) to manage Automatic Storage Managemernt (AsM) disks.

It succeeds and needs to be enabled to capture all SQL statements that require either the specified privileges or any privilege granted to the HR_ADMIN or OE_ADMIN role.

It fails because the command does notspecify when the unified audit policy should be enforced.

It succeeds and starts capturing only successful SQL statements for all users who have either the specified privileges or roles granted to them.

It fails because system privileges cannot be granted with roles in the same audit policy.

Control file backups can be created while connected to the root container.

Archived Redo Log backups can be created while connected to an application root CDB.

Control file backups can be created while connected to a nonroot container.

Online Redo Log backups can be created while connected to the root container.

The BACKUP TABLESPACE command can back up a PDB tablespace even if RMAN is connected to CDB$ROOT.

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.

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.

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.

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.

to switch to a patched Oracle Database home

to upgrade an Oracle Database on the centralized Rapid Home Provisioning server

to move an Oracle Database to the centralized Rapid Home Provisioning server

to switch back to the previous Oracle home as part of a rollback operation

to switch to a read-only Oracle home

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.

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

SYSsessions,regardlessoftherolesthataresetinthesession

SYSTEMsessions,regardlessoftherolesthataresetinthesession

SCOTT sessions, only if the MGR role is set in the session

SCOTT sessions, only if the MGR role is granted to SCOTT

SCOTTsessions,becauseheistheownerofthetable

SYSTEM session, only if the MGR role is set in the session

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.

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.

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

Database Replay

Automatic Database Diagnostic Monitor (ADDM) Compare Period report

Active Session History (ASH) report

SQL Performance Analyzer

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

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

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.

A duplexed backup set uses the same number of SBT channels as a non-duplexed backup set for the same number of files.

A non-duplexed backup set written to disk can be duplexed to disk by backing up the backup set that is already on disk.

A non-duplexed backup set written to SBT can be duplexed to tape by backing up the backup set that is already on tape.

A non-duplexed backup set written to disk can be duplexed to tape by backing up the backup set that is already on disk.

A non-duplexed backup set written to SBT can be duplexed to disk by backing up the backup set that is already on tape.

A duplexed backup set always uses twice as many SBT channels as a non-duplexed backup set for the same number of files.

If an RMAN BACKUP VALIDATE command takesroughly the same time as an actual backup, then both read and write I/O are likely bottlenecks.

Setting DBWR_IO_SLAVES to a non zero value can improve backup performance when using synchronous I/O.

If an RMAN BACKUP VALIDATE command takes noticeably lessthan an actual backup, then write I/O is a likely bottleneck.

If an RMAN BACKUP VALIDATE command takesroughly the same time as an actual backup, then read I/O is a likely bottleneck.

Data files with a high value in V$BACKUP_SYNC_IO.DISCRETE_BYTES_PER_SECOND are a potential performance bottleneck when synchronous I/O is used.

Setting DBWR_IO_SLAVES to a non zero value can improve backup performance when using asynchronous I/O/

Data files with a high value in V$BACKUP_ASYNC_IO.SHORT_WAITS are a potential performance bottleneck when asynchronous I/O is used.

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.

The NOREDO clause must be used if the backups of the database being duplicated were taken when the database was in NOARCHIVELOG mode.

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

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

The NOREDO clause can be used if the backups of the database being duplicated were taken when the database was in ARCHIVE LOG mode.

RMAN SBT-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 recovery catalog and the TARGET database is closed.

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

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.

Plugging the application root into a different CDB plugs in all its application PDBs.

The application root of an application container should be plugged into the other CDB before its application PDBs are plugged in.

Application PDBs in the application container must be unplugged before the application root is unplugged.

Unplugging the application root from a CDB unplugs all its application PDBs.

It requires only local UNDO mode in the database where the application container will be unplugged.

It requires local UNDO mode in both container databases.

To use it, Flashback Database must be enabled.

A block being recovered is not accessible.

It cannot repair logical corruption.

It can be performed on noncorrupt blocks.

The target database for which one or more blocks are to be recovered must be in the OPEN state.

The data file containing the block being recovered remains online.

By default, AWR snapshots are taken every 60 minutes.

Its collection level is determined by the value of the STATISTICS_LEVEL database parameter.

By default, AWR snapshots are retained for 7 days.

The taking of AWR snapshots can be disabled.

AWR data is stored in the SYSTEM tablespace.

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.

Re-enableredactionpoliciesthatuseFULLdataredaction.

Re-createredactionpoliciesthatuseFULLdataredaction.

Re-connect the sessions that access objects with redaction policies defined on them.

Flushthesharedpool.

Restart the database instance. Correct

using RMAN stored scripts

creating encrypted backups

creating customized reports about a single database's backups

using the REPORT SCHEMA command to list a database's data files and tablespaces at times in the past

using the KEEP FOREVER clause with the BACKUP command

using the REPORT SCHEMA command to list a database's current data files and tablespaces

oracle will be an owner of the Oracle Inventory.

oracle must be the owner of every Oracle Database installation.

oracle can own an Oracle Database installation but not an Oracle Grid Infrastructure installation.

oracle will be granted the SYSASM privilege when installing the Oracle Database software.

The user account, oracle, and group, oinstall, can be used for all Oracle software installations.

when free space in a dictionary managed tablespace falls below a specified percentage

when free space in a locally managed tablespace falls below a specified percentage

when the total number of locked user account exceeds a specific value

when the number of logons per second exceeds a specific value

when a resumable statement is suspended

when the total number of logons exceeds a specific value

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

the backup retention policy

the backup optimization policy

the DB_CREATE_ONLINE_LOG_DEST_n parameter setting

the archived log deletion policy

the DB_RECOVERY_FILE_DEST parameter setting

using guaranteed UNDO retention

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.

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.

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.

redo logs

control files

all data dictionary metadata

user-defined PL/SQL packages

temporary tablespaces

mandatory Oracle-supplied PL/SQL packages

undo tablespaces

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.