Oracle OCP 1Z0 053 Q134(RMAN SBT PARALLELISM)
134.You are managing an Oracle Database 11g database. You want to take a backup on tape drives of
the USERS tablespace that has a single data file of 900 MB. You have tape drives of 300 MB each. To
accomplish the backup, you issued the following RMAN command:
RMAN>BACKUP
SECTION SIZE 300M
TABLESPACE users;
What configuration should be effected to accomplish faster and optimized backups by using the above
command?
A. The SBT channel must be configured, with the default parallelism setting for the SBT device set to 1.
B. The COMPATIBLE initialization parameter for the database instance must be set to at least 10.0.
C. The SBT channel must be configured, with the parallelism setting for the SBT device set to 3.
D. The SBT channel must be configured, with the MAXPIECESIZE set to 300 MB.
Answer: C
參考:http://blog.csdn.net/rlhua/article/details/14228765
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.
the USERS tablespace that has a single data file of 900 MB. You have tape drives of 300 MB each. To
accomplish the backup, you issued the following RMAN command:
RMAN>BACKUP
SECTION SIZE 300M
TABLESPACE users;
What configuration should be effected to accomplish faster and optimized backups by using the above
command?
A. The SBT channel must be configured, with the default parallelism setting for the SBT device set to 1.
B. The COMPATIBLE initialization parameter for the database instance must be set to at least 10.0.
C. The SBT channel must be configured, with the parallelism setting for the SBT device set to 3.
D. The SBT channel must be configured, with the MAXPIECESIZE set to 300 MB.
Answer: C
參考:http://blog.csdn.net/rlhua/article/details/14228765
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.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/8520577/viewspace-2074549/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Oracle OCP 1Z0 053 Q500(Rman)Oracle
- Oracle OCP 1Z0 053 Q182(RMAN)Oracle
- Oracle OCP 1Z0 053 Q21(RMAN Duplicate)Oracle
- Oracle OCP 1Z0 053 Q600(RMAN BACKUP)Oracle
- Oracle OCP 1Z0 053 Q700(RMAN Duplicate)Oracle
- Oracle OCP 1Z0 053 Q703(Rman Backup)Oracle
- Oracle OCP 1Z0 053 Q342(RMAN BACKUP DURATION)Oracle
- Oracle OCP 1Z0 053 Q62(RMAN&ASM)OracleASM
- Oracle OCP 1Z0 053 Q564(Datafile Recovery with RMAN)Oracle
- Oracle OCP 1Z0 053 Q507(Rman Recovery)Oracle
- Oracle OCP 1Z0 053 Q79(RMAN Recover Image Copy)Oracle
- Oracle OCP 1Z0 053 Q505(RMAN DATAFILE BACKUP COPIES)Oracle
- Oracle OCP 1Z0 053 Q197(RMAN Report)Oracle
- Oracle OCP 1Z0 053 Q338(RMAN Expired Backup)Oracle
- Oracle OCP 1Z0 053 Q688(RMAN Backup Compression)Oracle
- Oracle OCP 1Z0 053 Q652(RMAN Configure Rate)Oracle
- Oracle OCP 1Z0 053 Q662(rman change tracking file)Oracle
- Oracle OCP 1Z0 053 Q348(RMAN Minimize Load)Oracle
- Oracle OCP 1Z0 053 Q94(RMAN SET COMMAND ID)Oracle
- Oracle OCP 1Z0 053 Q78(RMAN&change tracking file)Oracle
- Oracle OCP 1Z0 053 Q264(rman List&Report)Oracle
- Oracle OCP 1Z0 053 Q650Oracle
- Oracle OCP 1Z0 053 Q324Oracle
- Oracle OCP 1Z0 053 Q27Oracle
- Oracle OCP 1Z0 053 Q49Oracle
- Oracle OCP 1Z0 053 Q10Oracle
- Oracle OCP 1Z0 053 Q685Oracle
- Oracle OCP 1Z0 053 Q454Oracle
- Oracle OCP 1Z0 053 Q500Oracle
- Oracle OCP 1Z0 053 Q444(Scheduler)Oracle
- Oracle OCP 1Z0 053 Q440(Scheduler)Oracle
- Oracle OCP 1Z0 053 Q601Oracle
- Oracle OCP 1Z0 053 Q472(Locale)Oracle
- Oracle OCP 1Z0 053 Q525(ASM)OracleASM
- Oracle OCP 1Z0 053 Q292(NFS)OracleNFS
- Oracle OCP 1Z0 053 Q538(ASM)OracleASM
- Oracle OCP 1Z0 053 Q416Oracle
- Oracle OCP 1Z0 053 Q648(Flashback)Oracle