 |
|
Oracle Using
the Database Control to Configure Backups
Oracle Tips by Burleson Consulting |
This
is an excerpt from "Oracle 10g New Features for Administrators" by
Ahmed Baraka.
On the Database Control home page, follow the links:
Maintenance tab | Configure Backup Settings.
You can use one of the following choices to tell
RMAN where to place its target files:
o FORMAT option in a backup command
o CONFIGURE CHANNEL FORMAT option
o DB_RECOVERY_FILE_DEST
Implementing Fast Recovery
For those special times when you really need a fast
recovery, Oracle Database 10g offers the SWITCH DATABASE command.
The RMAN simply adjusts the pointers for the
datafiles in the control file, so they now point to the backup files
in your flash recovery area.
RMAN> SWITCH
DATABASE TO COPY
Note: Consider this fast recovery method as a
temporary solution. Later, you should relocate your database
datafiles to permanent locations.
This method applies in the tablespace level as well:
RMAN> sql 'alter
tablespace users offline';
RMAN> switch datafile 4 to copy;
RMAN> recover datafile 4;
RMAN> sql 'alter tablespace users online';
Recovering Datafiles without Backups
The ability to recover a file that has never been
backed up has always been available from SQL*Plus, with the help of
the CREATE DATAFILE .. AS .. statement. Now, in Oracle Database 10g,
you can create the lost file as part of an RMAN RESTORE DATABASE
command.
Simplified Recovery Through RESETLOGS
• In Oracle Database 10g, you can use backups taken
before an incomplete recovery operation; that is, you can use
backups from older incarnations of the database.
• The new archive redo log format in Oracle Database
10g is of the following form:
LOG_ARCHIVE_FORMAT="log%t_%s_%r.arc"
The additional variable r stands for the RESETLOGS
identifier.
• The V$DATABASE view contains now RESETLOGS_CHANGE#,
RESETLOGS_TIME, and RESETLOGS_ID.
• The V$LOG_HISTORY contains now RESETLOGS_CHANGE#
and RESETLOGS.
Dropping a Database
Here are some features of the DROP DATABASE command:
• Oracle will drop all control files and datafiles
automatically, whether you use the SQL*Plus, RMAN, or DBCA interface
to drop a database.
• Oracle does not remove archived redo logs and
backups. To make the RMAN remove all database backup copies as well
as the archived redo log files:
RMAN> DROP
DATABASE INCLUDING BACKUPS
• If you are using SPFILE, Oracle will remove it
automatically.
• After you drop a database, the RMAN catalog
continues to list the dropped database information.
You need to use the following RMAN command:
RMAN> UNREGISTER
DATABASE
Specifying Limits for Backup Duration
You can use the DURATION command as an option for
your regular backup commands, such as BACKUP AS COPY, to specify the
time (in hours and minutes) a backup job can take. This makes the
job taken less resources during its operation.
DURATION <hrs>:<mins>
[PARTIAL] [MINIMIZE {TIME|LOAD}]
PARTIAL - Normally, when your database backup jobs
run past the time interval you specify through the DURATION
parameter, the RMAN job errors out and the backup is canceled. You
can override this default behavior by specifying the PARTIAL clause,
which will prevent the issuing of any RMAN error messages.
MINIMIZE TIME - This option tells the RMAN to "hurry
up" and finish as fast as it can.
MINIMIZE LOAD - This option tells the RMAN to "slow
down" if it is well within its allotted time for a backup job.
Note: It is recommended that you do not use the
MINIMIZE LOAD option with tape.
 |
If you like Oracle tuning, see the
book "Oracle
Tuning: The Definitive Reference", with 950 pages of tuning
tips and scripts.
You can buy it direct from the publisher for 30%-off and get
instant access to the code depot of Oracle tuning scripts. |