Which four are true about a Recovery Manager (RMAN) duplication without a TARGET connection? (Choose four.)
Which four are true about a Recovery Manager (RMAN) duplication without a TARGET connection? (Choose four.)
When performing an RMAN duplication without a TARGET connection, the NOREDO clause must be used if the backups were taken when the database was in NOARCHIVELOG mode, ensuring that no archived redo logs are applied during recovery. The NOREDO clause can also be used for backups taken when the database was in ARCHIVELOG mode if the intention is not to apply redo logs. RMAN SBT-based backups and disk-based backups of the database can be used by the auxiliary instance in such a scenario. The UNDO TABLESPACE clause, contrary to some misconceptions, is not always required but only when duplicating a subset of tablespaces.
Correct answers are: A,D,E,H wrong: B,F,H: not "always" are required wrong: C: RMAN doesn't pushes the backup, but read from the backup.
Not BFG : https://docs.oracle.com/en/database/oracle/oracle-database/19/rcmrf/DUPLICATE.html UNDO TABLESPACE - This option is only required when a subset of tablespaces are being duplicated with the SKIP TABLESPACE and TABLESPACE clauses and this question does not speak about subset of tablespaces. Remain:ACDEH Not C : rman duplicate runs at auxiliary instance. Why should it push something via network? For me correct is: ADEH
I take all quotes, that support my statements, from: https://docs.oracle.com/en/database/oracle/oracle-database/19/rcmrf/DUPLICATE.html A is correct: "Therefore, you must use the NOREDO option when the source database was in NOARCHIVELOG mode when the backups were taken." D is correct: "You can also use the NOREDO option when you do not want to apply archived redo log files to a consistent backup." F is correct: "UNDO TABLESPACE tablespace_name Specifies the names of the tablespaces with undo segments. This option is only required when a subset of tablespaces are being duplicated with the SKIP TABLESPACE and TABLESPACE clauses. You must provide the list of tablespaces with undo segments in the following cases: No connection to the target database or the recovery catalog" H is correct: "Backup-based duplication without a connection to target or a recovery catalog RMAN creates duplicate files from RMAN backups and copies that were placed in a designated BACKUP LOCATION." Therefore, ADFH are all correct
A D F H is correct A. D. Because: For backup-based duplication of databases without a connection to the target database, RMAN cannot determine whether the source database was in NOARCHIVELOG mode. Therefore, you must use the NOREDO option when the source database was in NOARCHIVELOG mode when the backups were taken. You can also use the NOREDO option when you do not want to apply archived redo log files to a consistent backup. F. Because: You must provide the list of tablespaces with undo segments in the following cases: No connection to the target database or the recovery catalog No connection to a recovery catalog, a connection to the target but the target database is not open. H. Beacuse: You perform duplication by connecting to the auxiliary instance and using backups or copies of the source database that are stored in a disk location on the destination host. RMAN obtains metadata about where the backups and copies reside from the BACKUP LOCATION clause of the DUPLICATE command.
E Is incorrect This method is not supported for backups that are stored on tape devices Backup and Recovery User's Guide Page 662
A, E, F, H
G_C please read another time your article: UNDO TABLESPACE is need only when you duplicate a SUBSET of tablespaces
A E F H is correct for me
Incredibly wrong answers in comments. SBT backups cannot be used in a duplication without target connection, which is explicitly described in the documentation: " This method is not supported for backups that are stored on tape devices" REF:https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/rman-duplicating-databases.html#GUID-75463819-F48F-442F-904B-1B4CDB3711CC The others can be validated on DUPLICATE reference: https://docs.oracle.com/en/database/oracle/oracle-database/19/rcmrf/DUPLICATE.html#GUID-E13D8A02-80F9-49A2-9C31-92DD3A795CE4
A) https://docs.oracle.com/database/121/RCMRF/rcmsynta020.htm#RCMRF126 E) DUPLICATE ACTIVE DATABASE USING BACKUPSET new feature from 12R1 F) https://docs.oracle.com/cd/E25178_01/backup.1111/e10642/rcmdupad.htm H) DUPLICATE (...) BACKUP LOCATION
I change my mind answer F is incorrect because of that phrase "no connection exists to the recovery catalog", so answer D is correct because it can be i.e. after perform duplicate using consistent database backup. Generally: ADEH
Read twice before ... sorry guys D is of course INCORRECT
A, D, E, H are correct. F is NOT correct because of simple example I've just tested: rman auxiliary / run { allocate auxiliary channel ch1 type disk; DUPLICATE DATABASE PROD to TEST BACKUP LOCATION 'D:\Oracle\BACKUPS' NOFILENAMECHECK; }
E Is incorrect This method is not supported for backups that are stored on tape devices Backup and Recovery User's Guide Page 662
All duplication techniques require a connection to the auxiliary instance. Duplicating an Active Database with “Push” RMAN connects as TARGET to the source database instance and as AUXILIARY to the auxiliary instance The pull method requires connections to target and auxiliary instances. UNDO TABLESPACE Must be specified when target database is not open and there is no recovery catalog connection so that RMAN does not check the tablespace for SYS-owned objects NOREDO Signals RMAN that the application of redo logs should be suppressed during recovery Must be used with targetless DUPLICATE when target database is in NOARCHIVELOG mode at backup time Can also be used to explicitly state that no archived redo log files should be applied AEFH
ADEH, Undo tablespace is not requeried and rman doesn't push backup
A E F H F is okay - https://docs.oracle.com/en/error-help/db/rman-05521/ Cause A DUPLICATE was attempted when target database was not open without connection to a recovery catalog. It is necessary that the list of tablespaces with undo segments is provided with the UNDO TABLESPACE clause. Action Retry the command specifying the list of tablespaces with undo segments using the UNDO TABLESPACE clause. B
D may not okay becuase RMAN-05540 RMAN-05540: no archived logs found in repository for database string Cause: Recovery catalog did not have archived log records for the specified database. If database is running in NOARCHIVELOG mode, then specify NOREDO. Action: Specify NOREDO for NOARCHIVELOG databases. Cannot duplicate an ARCHIVELOG database unless the recovery catalog or target database control file has archived redo log information about it.
Change my mind ADEH F - not always, it depends https://docs.oracle.com/en/database/oracle/oracle-database/18/rcmrf/DUPLICATE.html#GUID-E13D8A02-80F9-49A2-9C31-92DD3A795CE4 You must provide the list of tablespaces with undo segments in the following cases: No connection to the target database or the recovery catalog No connection to a recovery catalog, a connection to the target but the target database is not open. Table 2-6 Prerequisites for Three Modes of Backup-Based Duplication If you duplicate a subset of tablespaces, and if the source database is not open, then any duplicated tablespaces with undo segments must be listed in the UNDO TABLESPACE clause. Target Connection > Yes (if no catalog used and target is not open)
Specifies the names of the tablespaces with undo segments. This option is only required when a subset of tablespaces are being duplicated with the SKIP TABLESPACE and TABLESPACE clauses. You must provide the list of tablespaces with undo segments in the following cases: No connection to the target database or the recovery catalog No connection to a recovery catalog, a connection to the target but the target database is not open. DUPLICATE reference for 19c. So F seems true. About E: >E Is incorrect This method is not supported for backups that are stored on tape devices Backup and Recovery User's Guide Page 662 True, but the it's about " Backup-Based Duplication Without a Target Database and Recovery Catalog Connection" so i think you can still do it without Target DB connection when you have Recovery Catalog connection - not sure. E could also be true, but F is right there in the documentation.
although "This option is only required when a subset of tablespaces are being duplicated with the SKIP TABLESPACE and TABLESPACE clauses". So maybe the point is that when you duplicate subset of tbs AND you don't have connection to catalog, then you have to specify the clause. It would make F false in favour of E. Tough call.
to catalog and target*
A,D, F G
Student Guide NOREDO signals RMAN that the applications of redo logs should be suppressed during recovery must be used with targetless duplicate when target db is noarchivelog mode at backup time can also be used to explictly state that no archived redo log files should be applied UNDO Tablespace must be specified when target database is not open and there is no recovery catalog connection so that RMAN does not check tablespace for SYS owned objects sorry i meant A,E,F,H and both SBT and disk based backup can be used by auxiliary instance.
I agree with that - AEFH.
It is ACEH, A. The NOREDO clause must be used if the backups of the database being duplicated were taken when the database was in NOARCHIVELOG mode. C. RMAN "pushes" the backups of the database to be duplicated over the network to the auxiliary instance. E. RMAN SBT-based backups of the database to be duplicated can be used by the auxiliary instance. H. RMAN disk-based backups of the database to be duplicated can be used by the auxiliary instance.
B is incorrect "always" required when no connection to target. this is NOT required in case of recovery catalog.
F is incorrect. the undo tablespace is "always" > not the case, only if you want to duplicate a subset of tablespaces
AE correct: Applies no archived redo log files when recovering a consistent backup in any of the following scenarios: You do not want to apply archived redo log files to the consistent backup even though the archived redo log files are available. The source database was running in NOARCHIVELOG mode at backup time and DUPLICATE is not connected to the target database. The source database is currently running in ARCHIVELOG mode but the backup was taken when the database was in NOARCHIVELOG mode.
ADEH for me!