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 usesection sizefor 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:
A,B, C,E,G works fine
C does not work. section size clause works only for datafiles – not for archivelogs
RMAN> BACKUP TABLESPACE “UNDO” INCLUDE CURRENT CONTROLFILE SECTION SIZE 100M;
Starting backup at 10-JUN-14
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=101 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 06/10/2014 11:55:32
RMAN-20202: Tablespace not found in the recovery catalog
RMAN-06019: could not translate tablespace name “UNDO”
RMAN> BACKUP TABLESPACE TEMP SECTION SIZE 10M;
Starting backup at 10-JUN-14
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 06/10/2014 12:31:14
RMAN-20202: Tablespace not found in the recovery catalog
RMAN-06019: could not translate tablespace name “TEMP”
What´s the name of the your UNDO tablespace ?
In my test, works !
E)
BACKUP TABLESPACE “UNDOTBS1” INCLUDE CURRENT CONTROLFILE SECTION SIZE 100M;
===========================================================================
RMAN> BACKUP TABLESPACE “UNDOTBS1” INCLUDE CURRENT CONTROLFILE SECTION SIZE 100M;
Starting backup at 26/07/2014 10:58:16
using channel ORA_DISK_1
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/CDB12c/undotbs01.dbf
channel ORA_DISK_1: starting piece 1 at 26/07/2014 10:58:16
channel ORA_DISK_1: finished piece 1 at 26/07/2014 10:58:17
piece handle=/u01/app/oracle/oradata/CDB12C/backupset/2014_07_26/o1_mf_nnndf_TAG20140726T105816_9x7dzrn3_.bkp tag=TAG20140726T105816 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
including current control file in backup set
channel ORA_DISK_1: starting piece 1 at 26/07/2014 10:58:18
channel ORA_DISK_1: finished piece 1 at 26/07/2014 10:58:20
piece handle=/u01/app/oracle/oradata/CDB12C/backupset/2014_07_26/o1_mf_ncnnf_TAG20140726T105816_9x7dzv2d_.bkp tag=TAG20140726T105816 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 26/07/2014 10:58:20
Starting Control File Autobackup at 26/07/2014 10:58:20
piece handle=/u01/app/oracle/oradata/CDB12C/autobackup/2014_07_26/o1_mf_n_853930700_9x7dzy0z_.bkp comment=NONE
Finished Control File Autobackup at 26/07/2014 10:58:23
>>> A,B,C,E,G works fine
Hi Sam,
Check your UNDO tablespace name
A – TRUE – WORK
B – TRUE – WORK – new option in 12c – Backups Using Image Copies
E – TRUE
G – TRUE
D – FALSE – RMAN newer backup tempolary TS
F – FALSE – command work but not produce multi-section backup
C – FALSE – command work but not produce multi-section backup
ABEG
ABEG
A : OK
B : OK but all merge as file
C : OK but don’t following section size.
D : OK if temp is real TS ( not internal temp TS )
E : OK
F : OK but size to small so just create 1
G : OK
A,E,G are correct.
and guess B
select backup_type, controlfile_included, incremental_level, pieces, block_size, multi_section
from v$backup_set
order by start_time;
B CON INCREMENTAL_LEVEL PIECES BLOCK_SIZE MUL
– — —————– ———- ———- —
D NO 8 8192 YES <= A
D YES 1 16384 NO
D YES 1 16384 NO
L NO 1 512 NO <= C
D YES 1 16384 NO
D NO 2 8192 YES <= E
D YES 1 16384 NO
D YES 1 16384 NO
D NO 1 16384 NO <= F
D YES 1 16384 NO
I NO 0 8 8192 YES <= G
D YES 1 16384 NO
ABEG is final answer
I agree!
Not C as the commands is for large datafiles not archivelogs
ABEG
All works in 12C.
Suppose “TEMP” is real table space name.
“BACKUP AS COPY TABLESPACE SYSTEM SECTION SIZE 100M” works even it did not split the file in output.
I agree, All works in 12c.
To create level 0 multisection incremental backups, the COMPATIBLE parameter must be set to 11.0 or higher. However, to create multisection incremental backups of level 1 or higher, you must set the COMPATIBLE parameter to 12.0.0 or higher. RMAN always creates multisection incremental backups with FILESPERSET set to 1.
Ref: http://docs.oracle.com/database/121/BRADV/rcmbckba.htm#BRADV380
New in 12c
Multi-Section Image Copy and Incremental Backups –
http://www.oracle.com/technetwork/database/features/availability/rman-overview-096633.html
Looks like this question is for the 11g
In this question you are jerks dudes!
ABEG
ABEG
ABEG
ADEG – This question is kind of jacked up in my opinion, the only way it makes sense is if you say “can” produce multi-section backups(IE the tablespaces are big enough to allow multiple pieces to be created given the answers SECTION SIZES) and you interpret “produce” to mean that multiple pieces exist after the backup is done. You also must consider that you changed the default temp tablespace name from “TEMP” to something else and created your own “TEMP” tablespace, such that the D command will work. I tried out A, G and E specifically on my system with success. I’m too lazy to validate D but why wouldn’t it work TEMP would just be a user created tablespace.
I forgot to say C doesn’t work tried it specifically, the command will work but the archivelogs are assembled into a single backup piece(not multi-section). THe SPFILE backup will not produce multiple pieces because the SPFILE is so small. B will not work because altho the file is split up DURING the operation after it’s over it is reassembled into one file.
ABEG