A database is running in archivelog mode. The database contains locally managed
tablespaces. Examine the RMAN command:
RMAN> BACKUP
AS COMPRESSED BACKUPSET
SECTION SIZE 1024M
DATABASE;
Which statement is true about the execution of the command?
A.
The backup succeeds only if all the tablespaces are locally managed.
B.
The backup succeeds only if the RMAN default device for backup is set to disk.
C.
The backup fails because you cannot specify section size for a compressed backup.
D.
The backup succeeds and only the used blocks are backed up with a maximum backup
piece size of 1024 MB.
Correct answer is D
COMPRESSED Enables binary compression.
RMAN compresses the data written into the backup set to reduce the overall size of the backup set. All backups that create backup sets can create compressed backup sets. Restoring compressed backup sets is no different from restoring uncompressed backup sets.
RMAN applies a binary compression algorithm as it writes data to backup sets. This compression is similar to the compression provided by many media manager vendors. When backing up to a locally attached tape device, compression provided by the media management vendor is usually preferable to the binary compression provided by BACKUP AS COMPRESSED BACKUPSET. Therefore, use uncompressed backup sets and turn on the compression provided by the media management vendor when backing up to locally attached tape devices. You should not use RMAN binary compression and media manager compression together.
Some CPU overhead is associated with compressing backup sets. If the target database is running at or near its maximum load, then you may find the overhead unacceptable. In most other circumstances, compressing backup sets saves enough disk space to be worth the CPU overhead.
SECTION SIZE sizeSpec Specifies the size of each backup section produced during a data file backup.
By setting this parameter, RMAN can create a multisection backup. In a multisection backup, RMAN creates a backup piece that contains one file section, which is a contiguous range of blocks in a file. All sections of a multisection backup are the same size. You can create a multisection backup for a data file, but not a data file copy.
File sections enable RMAN to create multiple steps for the backup of a single large data file. RMAN channels can process each step independently and in parallel, with each channel producing one section of a multisection backup set.
If you specify a section size that is larger than the size of the file, then RMAN does not use multisection backup for the file. If you specify a small section size that would produce more than 256 sections, then RMAN increases the section size to a value that results in exactly 256 sections.
Depending on where you specify this parameter in the RMAN syntax, you can specify different section sizes for different files in the same backup job.
Note: You cannot use SECTION SIZE with MAXPIECESIZE or with INCREMENTAL LEVEL 1.
I don’t think D. I tested and B is correct.
RMAN> CONFIGURE DEFAULT DEVICE TYPE TO STB_TAPE;
old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO ‘A’;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO ‘STB_TAPE’;
new RMAN configuration parameters are successfully stored
RMAN> BACKUP
2> AS COMPRESSED BACKUPSET
3> SECTION SIZE 1024M
4> DATABASE;
Starting backup at 18-NOV-15
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 11/18/2015 15:22:38
ORA-19554: error allocating device, device type: STB_TAPE, device name:
ORA-27001: unsupported device type
RMAN>
It is D,
You have probably misconfigured your tape device.
I am wrong. Thanks KenKendey!
D tested.
RMAN> configure channel device type sbt parms=’SBT_LIBRARY=oracle.disksbt,ENV=(BACKUP_DIR=/tape)’;
CONFIGURE DEFAULT DEVICE TYPE TO sbt;old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE ‘SBT_TAPE’ PARMS ‘SBT_LIBRARY=oracle.disksbt,ENV=(BACKUP_DIR=/tape)’;
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE ‘SBT_TAPE’ PARMS ‘SBT_LIBRARY=oracle.disksbt,ENV=(BACKUP_DIR=/tape)’;
new RMAN configuration parameters are successfully stored
released channel: ORA_SBT_TAPE_1
RMAN>
old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO ‘SBT_TAPE’;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO ‘SBT_TAPE’;
new RMAN configuration parameters are successfully stored
RMAN>
RMAN> BACKUP
2> AS COMPRESSED BACKUPSET
3> SECTION SIZE 1024M
4> DATABASE;
Starting backup at 30-DEC-15
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=73 device type=SBT_TAPE
channel ORA_SBT_TAPE_1: WARNING: Oracle Test Disk API
channel ORA_SBT_TAPE_1: starting compressed full datafile backup set
channel ORA_SBT_TAPE_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/orcl/system01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/orcl/sysaux01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/orcl/undotbs01.dbf
input datafile file number=00012 name=/u01/test.dbf
input datafile file number=00006 name=/u01/app/oracle/oradata/orcl/users01.dbf
channel ORA_SBT_TAPE_1: starting piece 1 at 30-DEC-15
D
D
D
D
D