Get Unlimited Contributor Access to the all ExamTopics Exams!
Take advantage of PDF Files for 1000+ Exams along with community discussions and pass IT Certification Exams Easily.
A - FALSE. The ARCH process backs up online redo logs (by creating Arch redo logs), never the DBA. DBAs backup Archive Redo Logs, not online redo logs.
B - TRUE. Control files are DB wide - backing them up, from the Container Root, is exactly where you do this.
C - TRUE. Part of the point of Multitenant is that you have control of all PDBs from the CDB level.
D - FALSE. An application root container is still below the main Container, so you cannot administer control files from here.
E - FALSE. For the same reason as above, you can only create control file backups from the Root Container.
So, BC is correct.
BE and C are correct
A. Online Redo Log backups can be created while connected to the root container.
FALSE - we don't backup online redo logs, we backup archived logs. ARCH backs up online redo
B. Control file backups can be created while connected to the root container.
TRUE - backup current controlfile;
C. The BACKUP TABLESPACE command can back up a PDB tablespace even if RMAN is connected to CDB$ROOT.
TRUE - backup tablepace pdb1:t1;
D. Archived Redo Log backups can be created while connected to an application root CDB.
FALSE - "skipping archived logs when connected to a PDB"
E. Control file backups can be created while connected to a nonroot container.
TRUE - During tests, I am able to backup a controlfile while connected to a nonroot container
I believe there are three correct answers to this question;
b) obvious answer
c) Tested in version 19.3: tablespace backup pdb1:tbs_name;
e) Tested on version 19.3 connected to pdb1: backup current controlfile;
Connected to:
Oracle Database 19c Standard Edition 2 Release 19.0.0.0.0 - Production
Version 19.12.0.0.0
SQL> SHOW PDBS
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED READ ONLY NO
3 PDB1 READ WRITE NO
SQL> alter session set container=PDB1;
Session altered.
SQL> ALTER DATABASE BACKUP CONTROLFILE TO '/tmp/control1.bak';
ALTER DATABASE BACKUP CONTROLFILE TO '/tmp/control1.bak'
*
ERROR at line 1:
ORA-65040: operation not allowed from within a pluggable database
SQL>
1)
RMAN> connect target "backup@pdb1 AS SYSBACKUP"
target database Password:
connected to target database: ORADB:PDB1 (DBID=1492547052)
RMAN> backup current controlfile;
Starting backup at 31-MAR-2022 07:51:08
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=279 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
channel ORA_DISK_1: starting piece 1 at 31-MAR-2022 07:51:10
channel ORA_DISK_1: finished piece 1 at 31-MAR-2022 07:51:11
piece handle=+DATADISK/ORADB/A98B865CBFAF359CE0537F01A8C08251/BACKUPSET/2022_03_31/ncnnf0_tag20220331t075109_0.292.1100764271 tag=TAG20220331T075109 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 31-MAR-2022 07:51:11
2) C - wrong, read docs.
C is true.
Alternatively, you can remove the ambiguity by qualifying the PDB name with the tablespace name when connected to the root container.
$ rman target=sys@cdb1
RMAN> BACKUP TABLESPACE pdb1:system, pdb1:sysaux, pdb1:users, pdb2:system;
https://oracle-base.com/articles/12c/multitenant-rman-backup-recovery-cdb-and-pdb-12cr1#tablespace-and-datafile-backups
B, C
not D :
when connected to application root PDB:
RMAN> backup archivelog all;
skipping archived logs when connected to a PDB
E , also correct, you can create cf backup:
backup current controlfile;
BC are perfectly correct but I think even E is correct. I connected to a PDB on my system and backed up controlfile.
target database Password:
connected to target database: CRYPTODB:PDB2 (DBID=1223325248)
RMAN> backup current controlfile;
Starting backup at 29-JUN-21
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=402 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
channel ORA_DISK_1: starting piece 1 at 29-JUN-21
channel ORA_DISK_1: finished piece 1 at 29-JUN-21
piece handle=H:\ORACLE\ORACLE19C\FRA2\CRYPTODB\195AE5877EB842D6AD88571743F1FBA0\BACKUPSET\2021_06_29\O1_MF_NCNNF_TAG20210629T200025_JFPCN4YJ_.BKP tag=TAG20210629T200025 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 29-JUN-21
upvoted 3 times
...
...
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
xRodge
Highly Voted 2 years, 9 months agoObserverPL
Highly Voted 2 years, 12 months ago7206e44
Most Recent 2 weeks, 5 days agoantonica
1 month, 2 weeks agoantonica
1 month, 3 weeks ago_gio_
10 months, 2 weeks agoScottL
1 year agovkra
1 year, 2 months agoflaviogcmelo
2 years agomtnetmaker
2 years, 1 month agomtnetmaker
2 years, 1 month agofreemun05
2 years, 1 month agojackymak
1 year, 3 months agoEric_F
2 years agoAldrid
3 years agomporislav
3 years agoRinD
3 years agodunhill
3 years agodunhill
2 years, 12 months agonavingupta52
2 years, 10 months ago