Identify four RMAN commands that produce a multi-section backup.

The persistent configuration settings for RMAN have default for all parameters.
Identify four RMAN commands that produce a multi-section backup.

The persistent configuration settings for RMAN have default for all parameters.
Identify four RMAN commands that produce a multi-section backup.

A.
BACKUP TABLESPACE SYSTEM SECTION SIZE 100M;

B.
BACKUP AS COPY TABLESPACE SYSTEM SECTION SIZE 100M;

C.
BACKUP ARCHIVELOG ALL SECTION SIZE 25M;

D.
BACKUP TABLESPACE “TEMP” SECTION SIZE 10M;

E.
BACKUP TABLESPACE “UNDO” INCLUDE CURRENT CONTROLFILE SECTION SIZE 100M;

F.
BACKUP SPFILE SECTION SIZE 1M;

G.
BACKUP INCREMENTAL LEVEL 0 TABLESPACE SYSAUX SECTION SIZE 100M;

Explanation:

Incorrect:
Not B: An image copy is an exact copy of a single datafile, archived redo log file, or control file.
Image copies are not stored in an RMAN-specific format. They are identical to the results of
copying a file with operating system commands. RMAN can use image copies during RMAN
restore and recover operations, and you can also use image copies with non-RMAN restore and
recovery techniques.
Not G: You cannot use section size for a full database backup.
Note:
* If you specify the SECTION SIZE parameter on the BACKUP command, then RMAN produces a
multisection backup. This is a backup of a single large file, produced by multiple channels in
parallel, each of which produces one backup piece. Each backup piece contains one file section of
the file being backed up.
* Some points to remember about multisection backups include:



Leave a Reply 11

Your email address will not be published. Required fields are marked *


Shawn

Shawn

A, B, E & G.

Oracle 12c supports multi-section image copies.
Temp is not backed up.
SECTION SIZE only applies to data files (not for archlogs, control files, spfiles, etc.).

Alexis

Alexis

Where to get that information?

smbd.smth

smbd.smth

i can’t understand why we need to backup TEMP or UNDO?
answer E is also with controlfile.

Noname

Noname

Guys, I ran the commands with default RMAN configuration. All commands except for D,E run successfully. But of the 5 successful executions, ACFG had multi-section backups. The image copy with section executes fine, but creates only one file of 700MB size(not multi-section).

My choice for answers will be ACFG.

ora600

ora600

A,B are correct. I tested it and it produces several backuppieces in both cases. The oracle documentation says that data file backups and data file copies work with SECTION SICE.

C is wrong. Does not create multiple backuppieces. I tested it with a 25MB archivelog and SECTION SIZE 1M

D is wrong. There is no need to back up a temp tablespace at all

E is correct. @smbd.smth backing up undo tbs is very importand during online backup. @Noname I guess u failed because your undo tablespace is not called “UNDO” in a 12c database the undo tbs is called “UNDOTBS1”. But the answer in general is correct. My test showed multiple backuppieces.

G is correct. See A and B.

pkg

pkg

ABEG – Correct.

2) A is correct ;

RMAN> backup tablespace undotbs1 include current controlfile section size 50M ;

Starting backup at 12-MAY-15
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=52 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00004 name=/u01/app/oracle/oradata/mycdb/undotbs01.dbf
backing up blocks 1 through 6400
channel ORA_DISK_1: starting piece 1 at 12-MAY-15
channel ORA_DISK_1: finished piece 1 at 12-MAY-15
piece handle=/u01/app/oracle/fast_recovery_area/MYCDB/backupset/2015_05_12/o1_mf_nnndf_TAG20150512T222707_bo4w1df6_.bkp tag=TAG20150512T222707 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:04
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00004 name=/u01/app/oracle/oradata/mycdb/undotbs01.dbf
backing up blocks 6401 through 12800
channel ORA_DISK_1: starting piece 2 at 12-MAY-15
channel ORA_DISK_1: finished piece 2 at 12-MAY-15
piece handle=/u01/app/oracle/fast_recovery_area/MYCDB/backupset/2015_05_12/o1_mf_nnndf_TAG20150512T222707_bo4w1j6t_.bkp tag=TAG20150512T222707 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00004 name=/u01/app/oracle/oradata/mycdb/undotbs01.dbf
backing up blocks 12801 through 19200
channel ORA_DISK_1: starting piece 3 at 12-MAY-15
channel ORA_DISK_1: finished piece 3 at 12-MAY-15
piece handle=/u01/app/oracle/fast_recovery_area/MYCDB/backupset/2015_05_12/o1_mf_nnndf_TAG20150512T222707_bo4w1k10_.bkp tag=TAG20150512T222707 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00004 name=/u01/app/oracle/oradata/mycdb/undotbs01.dbf
backing up blocks 19201 through 25600
channel ORA_DISK_1: starting piece 4 at 12-MAY-15
channel ORA_DISK_1: finished piece 4 at 12-MAY-15
piece handle=/u01/app/oracle/fast_recovery_area/MYCDB/backupset/2015_05_12

2) B is correct

RMAN> backup as copy tablespace system section size 100M ;

Starting backup at 12-MAY-15
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile copy
input datafile file number=00001 name=/u01/app/oracle/oradata/mycdb/system01.dbf
backing up blocks 1 through 12800
output file name=/u01/app/oracle/fast_recovery_area/MYCDB/datafile/o1_mf_system_bo4w9snr_.dbf tag=TAG20150512T223137
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:16
channel ORA_DISK_1: starting datafile copy
input datafile file number=00001 name=/u01/app/oracle/oradata/mycdb/system01.dbf
backing up blocks 12801 through 25600
output file name=/u01/app/oracle/fast_recovery_area/MYCDB/datafile/o1_mf_system_bo4w9snr_.dbf tag=TAG20150512T223137

4) C seems not working – Wrong answe r

RMAN> backup archivelog all section size 5M ;

Starting backup at 12-MAY-15
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=26 RECID=2 STAMP=879546735
input archived log thread=1 sequence=27 RECID=1 STAMP=879546728
input archived log thread=1 sequence=28 RECID=3 STAMP=879546891
input archived log thread=1 sequence=29 RECID=4 STAMP=879546928
channel ORA_DISK_1: starting piece 1 at 12-MAY-15
channel ORA_DISK_1: finished piece 1 at 12-MAY-15
piece handle=/u01/app/oracle/fast_recovery_area/MYCDB/backupset/2015_05_12/o1_mf_annnn_TAG20150512T223528_bo4wk0k0_.bkp tag=TAG20150512T223528 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07

MPC

MPC

A very important point to note here is in 12c

If we specify the SECTION SIZE larger than the actual Datafile size, then RMAN does not use the Multi-Section option.

MPC

MPC

From Oracle 12c RMAN, Multisection Backups are supported for the below.,

Backup using Backup sets and Image Copies.
Full Backups using Backup sets and Image Copies.
Incremental level 0 backups and higher than level 0