dbms-notes: writing blocks to disk

(Q) What initialization parameters are used to configure a Fast Recovery Area?

DB_RECOVERY_FILE_DEST - specifies default location for fast recovery area.
DB_RECOVERY_FILE_DEST_SIZE - specifies (in bytes) the hard limit on the total space to be used by target database recovery files created in the fast recovery area
(optional) DB_FLASHBACK_RETENTION_TARGET -Specifies the upper limit (minutes) on how far back in time the database may be flashed back.

(Q) Can you configure the Fast Recovery Area on an ASM disk group?

(Q) How large should you configure the Fast Recovery Area?

At an ABSOLUTE MINIMUM, it should be large enough to containt the archived redo logs not yet on tape.
Scenario:

If you use incrementally updated backups and set the backup retention policy to REDUNDANCY 1, you can determine the size of the fast recovery area as below:

(Q) Which statements about using RMAN to perform backups are correct?

( ) You CAN perform incremental backups with RMAN
( ) RMAN detects corrupt blocks and logs in V$DATABASE_BLOCK_CORRUPTION
( ) Automatically establishes name and locations of all files to be backed up
( ) Backups are recorded in the CONTROL FILE, which is the main repository of RMAN metadata.
( ) Optionally, you CAN store backup metadata in a recovery catalog, which should be a schema in a database different of the one backed up.
( ) The primary storage for RMAN repository information for a database is always in the control file of the database.
( ) RMAN supports proxy copy, a feature that allows a media manager to manage completely the transfer of data between disk and backup media
( ) RMAN backups init parameter file
( ) RMAN DOES NOT backup password and networking files.
( ) RMAN supports a platform-independent language for backups

(Q) What are the characteristics of Incremental Backups?

Store only blocks changed since a previous incremental (Level 0 or Level 1) backup
Provide more compact backups and faster recovery
Less redo logs are applied during recovery
If you enable block change tracking, then full table scans on input files will not be performed during recovery
You can take a Level 0 or Level 1 Incremental Backup

$ rman
RMAN> CONNECT TARGET /
RMAN> BACKUP
       INCREMENTAL LEVEL 1 CUMULATIVE
       SKIP INACCESSIBLE
       DATABASE;

The example above:

Pages