Oracle Database 11g: Administration II
Question No: 341 – (Topic 10)
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:
RMANgt;BACKUP SECTION SIZE 300M
What configuration should be effected to accomplish faster and optimized backups by using the above command?
The SBT channel must be configured, with the default parallelism setting for the SBT device set to 1.
The COMPATIBLE initialization parameter for the database instance must be set to at least 10.0.
The SBT channel must be configured, with the parallelism setting for the SBT device set to 3.
The SBT channel must be configured, with the MAXPIECESIZE set to 300 MB.
Answer: C Explanation:
Dividing the Backup of a Large Data File into Sections (link)
If you specify the SECTION SIZE parameter on the BACKUP command, then RMAN creates a backup set in which each backup piece contains the blocks from one file section. A file section is a contiguous range of blocks in a file. This type of backup is called a multisection backup.
Note: You cannot specify SECTION SIZE with MAXPIECESIZE.
The purpose of multisection backups is to enable RMAN channels to back up a single large
file in parallel. RMAN divides the work among multiple channels, with each channel backing up one file section in a file. Backing up a file in separate sections can improve the performance of backups of large datafiles.
If a multisection backup completes successfully, then none of the backup sets generated during the backup contain a partial data file. If a multisection backup is unsuccessful, then it is possible for the RMAN metadata to contain a record for a partial backup set. RMAN does not consider partial backups for restore and recovery. You must use the DELETE command to delete the partial 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.
To make a multisection backup:
Start RMAN and connect to a target database and recovery catalog (if used).
If necessary, configure channel parallelism so that RMAN can make the backup parallel.
Execute BACKUP with the SECTION SIZE parameter.
For example, suppose that the users tablespace contains a single data file of 900 MB. Also assume that three SBT channels are configured, with the parallelism setting for the SBT device set to 3. You can break up the data file in this tablespace into file sections as shown in the following example:
SECTION SIZE 300M
In this example, each of the three SBT channels backs up a 300 MB file section of the users data file.
Question No: 342 – (Topic 10)
Which statement describes the significance of the CHANGE FAILURE command in RMAN? (Choose all that apply.)
It is used to change failure priority only for HIGH or LOW priorities.
It is used to execute the advised repair script.
It is used to change failure priority only for the CRITICAL priority.
It is used to explicitly close the open failures.
It is used to inform the database about the repair after the repair script executes.
Question No: 343 – (Topic 10)
View the Exhibit and examine the output of the query in different times when the following command runs in an RMAN sessions:
RMANgt; BACKUP DATABASE FILESPERSET 2;
The database has seven data files. Why is the %_COMPLETE refreshed to 13.59 in the third output after reaching 88.77?
Because the progress is reported for each data file
Because the progress is reported for each backup set
Because other RMAN sessions have issued the same BACKUP command
Because new data files have been added to the database while the RMAN backup is in progress
Question No: 344 – (Topic 10)
You performed the RMAN database backup having a backupset key number 231 with the KEEP FOREVER option.
After some days, you want to change the status of the database backup and you issued the following command:
RMANgt;CHANGE BACKUPSET 231 NOKEEP;
What is the implication of this command?
The backup is deleted.
The backup is marked unavailable.
The backup overrides the backup retention policy.
the backup becomes eligible for deletion according to the existing retention policy
Question No: 345 – (Topic 10)
You performed the RMAN database backup with the KEEP option. Which two statements are true regarding this backup? (Choose two.)
The backup contains data files, the server parameter file, and the control file even if the control file autobackup is disabled.
The KEEP option overrides the configured retention policy.
The backup contains only data files and archived redo log files.
The KEEP option is an attribute of an individual backup piece.
Question No: 346 – (Topic 10)
You executed the following command in Recovery Manager (RMAN): RMANgt; REPORT NEED BACKUP days 3;
What is the output of this command?
a list of files that require a backup within three days
a list of files requiring more than 3 days of archive logs to apply
a list of files that RMAN recommends be backed up only once in every three days, based on low volatility
a list of files for which a backup has already been performed in the last three days and which is required to be backed up again based on the high number of transactions performed on them
Answer: B Explanation:
Using RMAN REPORT NEED BACKUP with Different Retention Policies (link)
You can specify different criteria for REPORT NEED BACKUP, using one of the following forms of the command:
REPORT NEED BACKUP RECOVERY WINDOW OF n DAYS
Displays objects requiring backup to satisfy a recovery window-based retention policy REPORT NEED BACKUP REDUNDANCY n
Displays objects requiring backup to satisfy a redundancy-based retention policy REPORT NEED BACKUP DAYS n
Displays files that require more than n days#39; worth of archived redo log files for recovery REPORT NEED BACKUP INCREMENTAL n
Displays files that require application of more than n incremental backups for recovery
Question No: 347 – (Topic 10)
Examine the following command used to perform incremental level 0 backup: RMANgt; BACKUP INCREMENTAL LEVEL 0 DATABASE;
To enable the block change tracking, after the incremental level 0 backup you issued the following command:
SQLgt; ALTER DATABASE ENABLE BLOCK CHANGE TRACKING USING FILE #39;/mydir/
To perform incremental level 1 cumulative backup, you issued the following command:
RMANgt; BACKUP INCREMENTAL LEVEL 1 CUMULATIVE DATABASE;
Which two statements are true in the above situation? (Choose two.)
The block change tracking data will be used only from the next incremental 0 backup.
The incremental backup will use change tracking data for accomplishing the backup.
The incremental backup will not use change tracking data for accomplishing the backup.
The block track file will scan all the blocks and create bitmap for all the blocks backed up in the level 0 backup.
Question No: 348 – (Topic 10)
Multiple RMAN sessions are connected to the database instance. Examine the following output when backup commands are running in server sessions: What could have helped you to correlate server sessions with channels?
Implement RMAN multiplexing
Set the DEBUG ON in the RMAN script
Specify the command ID in the RMAN script
Use a tag with the RMAN BACKUP command
Question No: 349 – (Topic 10)
A shoot-out has erupted between your MS development teams using .NET and your Linux development teams using Java. Knowing that your database is in danger, which command would you use to back up your NOARCHIVELOG mode database using RMAN with compression?
backup database all
backup compressed database
backup as compressed backupset database;
backup as compressed backup database plus archivelog all;
backup as compressed backupset database plus compress archivelog all;
Answer: A Explanation:
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/23/2014 11:46:01
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode RMANgt;
Question No: 350 – (Topic 10)
Which dynamic view displays the status of block-change tracking?
Answer: B Explanation:
V$BLOCK_CHANGE_TRACKING displays the status of block change tracking for the database.
|Lowest Price Guarantee||Yes||No||No|
|Free VCE Simulator||Yes||No||No|