Recovery Manager Advanced Techniques - Oracle 10g/11g Data and Database Management Utilities - page 109

The following rman command reads the corruption list and performs the block
recovery process without prompting the user for each individual block:
RMAN> BLOCKRECOVER CORRUPTION LIST;
Starting blockrecover at 26-OCT-08
using channel ORA_DISK_1
channel ORA_DISK_1: restoring block(s)
channel ORA_DISK_1: specifying block(s) to restore from backup set
restoring blocks of datafile 00005
More restore/recovery information is displayed:
media recovery complete, elapsed time: 00:00:10
Finished blockrecover at 26-OCT-08
The problem is solved and the information recorded in the V$DATABASE_BLOCK_
CORRUPTION dynamic view is automatically cleared once the problem is solved.
Backup duration and throttling
Performing a database backup is a task that consumes large amount of resources.
If the production system worked from nine to five, Monday to Friday, then we would
easily be able to find a maintenance window, which could be used to schedule the
costly backup operation. But what about a 24x7 system where it is very hard to find
a maintenance window where the backup task must fiercely compete with other
processes to gain access to CPU and I/O resources to achieve the task? The answer,
so far, is simple, the backup must be done, whatever the price to be paid.
Oracle 10g introduced a nice feature that allows the DBA to launch the backup
task reducing system resource consumption. It allows the DBA to control the
backup duration so that the backup may take longer but it will also consume fewer
system resources.