OCP Backup And Recovery — 10 Questions

Question 1

You need to perform a table-level point-in-time recovery. Which RMAN command syntax is correct?

Accepted Answer

RECOVER TABLE HR.EMPLOYEES UNTIL SCN 12345;. The correct RMAN command for table-level point-in-time recovery is RECOVER TABLE HR.EMPLOYEES UNTIL SCN 12345;. This command restores the specified table to a particular SCN by creating a temporary auxiliary instance, recovering the table, and then importing it back into the original database. It is designed for table-level recovery without affecting other tablespaces.

Answer

RESTORE TABLE ...

Answer

FLASHBACK TABLE ...

Answer

IMPORT TABLE ...

Question 2

Which TWO RMAN settings significantly improve performance during backup operations on an Exadata system?

Accepted Answer

CONFIGURE BACKUP OPTIMIZATION ON;. Option C, CONFIGURE BACKUP OPTIMIZATION ON, is correct because it enables RMAN to skip backing up datafiles or archived redo logs that are identical to previously backed-up versions, drastically reducing I/O and elapsed time on Exadata systems where large volumes of unchanged data exist. Option D, CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET, is correct because compressing backupsets reduces the amount of data written to disk and the associated I/O, which significantly improves backup performance on Exadata's high-throughput storage. Option A is incorrect because RATE 10M artificially throttles the channel to 10 MB/s, which would slow backups rather than improve performance. Option B is incorrect because MAXSETSIZE UNLIMITED does not enhance performance; it only removes the size limit per backupset and can even reduce parallelism. Option E is incorrect because disabling the controlfile autobackup removes a safety net and has no positive performance impact on backup operations.

Answer

CONFIGURE CHANNEL ... RATE 10M;

Answer

CONFIGURE MAXSETSIZE UNLIMITED;

Answer

CONFIGURE CONTROLFILE AUTOBACKUP OFF;

Question 3

You are migrating an Oracle 23ai database to a different platform with different endianness. Which RMAN command is used to convert the datafiles to the target platform format?

Accepted Answer

RMAN> CONVERT DATAFILE '...' TO PLATFORM '...' FROM PLATFORM '...';. The CONVERT DATAFILE command is required when the source and destination platforms have different endian formats.

Answer

RMAN> CONVERT DATABASE ON TARGET PLATFORM;

Answer

RMAN> RESTORE DATAFILE FROM PLATFORM;

Answer

ALTER DATABASE CONVERT TO PLATFORM;

Question 4

You are performing a cross-platform transportable tablespace migration from Linux to Windows. Which RMAN command is required to convert the datafiles for the destination platform?

Accepted Answer

CONVERT TABLESPACE ... TO PLATFORM 'Microsoft Windows x86 64-bit';. The CONVERT TABLESPACE command is used to change the endian format for cross-platform migrations.

Answer

ALTER TABLESPACE ... CONVERT;

Answer

RMAN TRANSPORT ...

Answer

RMAN COPY ...

Question 5

Your database is in ARCHIVELOG mode. You accidentally dropped a critical tablespace and need to perform a Tablespace Point-in-Time Recovery (TSPITR). What is the primary requirement for the auxiliary instance during this process?

Accepted Answer

The auxiliary instance must have enough disk space to hold the tablespace being recovered.. The primary requirement for the auxiliary instance during TSPITR is that it must have enough disk space to hold the tablespace being recovered, along with the SYSTEM, SYSAUX, and UNDO tablespaces needed to open the auxiliary database. RMAN automatically creates and manages the auxiliary instance, so manual startup or separate ORACLE_HOME is not required.

Answer

The auxiliary instance must have the same DBID as the target database.

Answer

The auxiliary instance must be configured with a separate ORACLE_HOME.

Answer

The auxiliary instance must be started in NOMOUNT mode manually by the DBA.

Question 6

Which TWO actions are required to enable Flashback Database on a production environment?

Accepted Answer

Ensure the database is in ARCHIVELOG mode.. Option B is correct because Flashback Database relies on archived redo logs and flashback logs to rewind the database, so the database must be running in ARCHIVELOG mode before you can enable it. Option D is correct because DB_FLASHBACK_RETENTION_TARGET specifies the upper limit, in minutes, on how far the database can be flashed back, and it must be set as part of configuring Flashback Database. Option A is wrong because UPGRADE mode is used for running upgrade scripts, not for enabling Flashback Database. Option C is wrong because DB_RECOVERY_FILE_DEST_SIZE must be set to a nonzero value to define the Fast Recovery Area size, not zero. Option E is wrong because existing restore points do not need to be dropped to enable Flashback Database.

Answer

Restart the database in UPGRADE mode.

Answer

Set DB_RECOVERY_FILE_DEST_SIZE to zero.

Answer

Drop all existing restore points.

Question 7

Which THREE features are required for using Flashback Database?

Accepted Answer

A Fast Recovery Area (FRA) must be configured.. Flashback Database requires a Fast Recovery Area (FRA) to be configured (option A), because the flashback logs and any needed archived redo logs are stored there, and the FRA provides the space management and retention needed for the flashback log files. The database must be in ARCHIVELOG mode (option C), since Flashback Database relies on archived redo log information to roll the database forward after restoring flashback log images. Flashback logs must be enabled (option E), typically by setting DB_FLASHBACK_RETENTION_TARGET and issuing ALTER DATABASE FLASHBACK ON, because these logs are the core mechanism that captures before-images of changed blocks. Option B is incorrect because NOARCHIVELOG mode is incompatible with Flashback Database, and option D is incorrect because the database does not need to be a standby; Flashback Database works on a primary or standalone database as well.

Answer

The database must be in NOARCHIVELOG mode.

Answer

The database must be a standby.

Question 8

Which TWO RMAN configurations are recommended to optimize backup performance in a high-transaction environment?

Accepted Answer

CONFIGURE DEVICE TYPE DISK PARALLELISM 4;. Option A is correct because CONFIGURE DEVICE TYPE DISK PARALLELISM 4 enables RMAN to use four parallel channels for disk backups, allowing multiple backup pieces to be written simultaneously and significantly improving throughput in a high-transaction environment. Option C is correct because ALTER DATABASE ENABLE BLOCK CHANGE TRACKING activates the block change tracking file, which lets RMAN perform fast incremental backups by reading only changed blocks instead of scanning the entire datafile, greatly reducing backup time and I/O load. Option B is not recommended here because compression consumes additional CPU resources, which can hurt performance in a high-transaction workload where CPU is already busy. Option D is incorrect because MAXSETSIZE limits the size of backup sets and can cause backup failures or fragmentation rather than optimizing performance. Option E is incorrect because disabling controlfile autobackup removes a critical recovery safeguard and does not improve backup performance.

Answer

CONFIGURE COMPRESSION ALGORITHM 'MEDIUM';

Answer

CONFIGURE MAXSETSIZE TO 10G;

Answer

CONFIGURE CONTROLFILE AUTOBACKUP OFF;

Question 9

You are configuring a RMAN backup strategy for a multitenant container database (CDB) and want to ensure that a backup of the root container also includes all PDBs. Which configuration command achieves this automatically?

Accepted Answer

BACKUP DATABASE. In a multitenant container database (CDB), the BACKUP DATABASE command automatically includes the root container and all pluggable databases (PDBs) by default. There is no need for additional configuration to include PDBs; RMAN backs up the entire CDB when you issue BACKUP DATABASE.

Answer

CONFIGURE INCLUDE PDB BACKUP ON

Answer

CONFIGURE CDB BACKUP ALL ON

Answer

BACKUP CONTAINER ALL

Question 10

Which THREE conditions must be met to perform a successful RMAN cross-platform transportable tablespace migration?

Accepted Answer

The RMAN CONVERT command must be used if endianness differs.. Option B is correct because when the source and target platforms have different endianness, RMAN's CONVERT TABLESPACE (or CONVERT DATAFILE) command must be used to transform the datafiles into the target platform's byte order. Option D is correct because a tablespace must be placed in READ ONLY mode before it can be transported, ensuring the datafiles are self-consistent and no further changes occur during the operation. Option E is correct because cross-platform transportable tablespace migration requires the database COMPATIBLE initialization parameter to be set to at least 11.0.0, which enables the necessary cross-platform conversion features. Option A is not required because differing endianness is handled by the CONVERT command, so the platforms need not share the same endian format. Option C is not required because the source and destination databases are independent and do not need matching DBIDs for a transportable tablespace migration.

Answer

The source platform must be the same endian as the target.

Answer

The source and destination databases must have the same DBID.