In the previous modules, we explored the different enhancements in Recovery Manager (RMAN) and backup strategies. In this module, we will look at the following new enhancements in backup and recovery:
- Improvements in export and import
- Duplex or multiple archive logs
- Detect and repair of corrupted blocks
- Reports and lists about backups
- V$ data dictionary views for backup and recovery
Starting with Oracle Database 10g, automatic archiving for an Oracle database is enabled with the following SQL command:
ALTER DATABASE ARCHIVELOG
If the database is in ARCHIVELOG mode, Oracle marks the redo logs for archiving as it fills them. The full log files must be archived before they can be reused. The ALTER DATABASE ARCHIVELOG command will by default turn on automatic
archiving and the archivers are started.
Prior to Oracle Database 10g, log files marked as ready for archiving did not mean they would be automatically archived. You also needed to set a parameter in the initialization file with the syntax:
LOG_ARCHIVE_START = TRUE
Setting this parameter started an Oracle process to copy a full redo log to the archive log destination.
The archive log destination and the format for the archived redo log names are specified using two additional parameters,
LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT. A setting such as the following:
LOG_ARCHIVE_DEST = C:\ORANT\DATABASE\ARCHIVE
specifies the directory to which Oracle writes the archived redo log files, and:
LOG_ARCHIVE_FORMAT = ORCL%t_%s_%r.arc
defines the format Oracle will use for the archived redo log filenames. In this case, the filenames will begin with ORCL and will end with .arc.
The parameters for the format wildcards are: