| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Diff between...CONTROLFILE: AUTOBACKUP / include current / backup current / copy current / Snapshot
CONTROLFILE: AUTOBACKUP / include current / backup current / copy = current / Snapshot
These are my personal notes regarding these RMAN controlfile topics;
I think I see why I previously never used "CONTROLFILE AUTOBACKUP".
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONTROLFILE AUTOBACKUP
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIGURE CONTROLFILE AUTOBACKUP ON | OFF | CLEAR;
Bug:2458246 RMAN WRONGLY THINKS BACKUPS WITH SPFILE ARE OBSOLETE =20
~~~~~~~~ =20
If you have RMAN backups that include the SPFILE, and you do either =
REPORT OBSOLETE or DELETE OBSOLETE with RMAN,=20
then RMAN might incorrectly report or delete certain backups as =
obsolete, even if they weren't. =20
~~~~~~~~~~~~ =20
1) Don't use the SPFILE ..instead use the init.ora parameter file =20
2) Include in your scripts...
RMAN> backup current controlfile; =20
This will add the controlfile in a different piece handle that the =
autobackup command. =20
3) Don't use the autobackup command. (set OFF) =20
~~~~~~~~~=20
Fixed in: 9.2.0.2 and 10i=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
include current controlfile
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
* include current controlfile - creates a snapshot of the current =
control file and places it into each backup set produced by this clause. =
NOTE: 9i *always* include a controlfile in the RMAN backup by default.
RMAN> BACKUP current controlfile =
FORMAT=3D'/a0004/export/dba9i/%d_controlfile_%u_%p_%c.bkp';
Starting backup at 01-OCT-03 using channel ORA_DISK_1 channel ORA_DISK_1: starting full datafile backupset channel ORA_DISK_1: specifying datafile(s) in backupset including current controlfile in backupset channel ORA_DISK_1: starting piece 1 at 01-OCT-03 channel ORA_DISK_1: finished piece 1 at 01-OCT-03 piece handle=3D/a0004/export/dba9i/DBA9I_controlfile_03f2pvqb_1_1.bkp = comment=3DNONE channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01 Finished backup at 01-OCT-03
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
copy current controlfile
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
This will generate a single (NON-RMAN) file copy of the current =
controlfile.
This command is equvilent to; SVRMGRL> alter database backup =
controlfile.
Even though you "include one in the atabase backup it IS BETTER to have =
one all by itself.
THE ONE WITH THE BACKUP DOES *NOT* HAVE CURRENT BACKUP INFO!!!!!
RMAN> run {allocate channel c1 type disk;
copy current controlfile to =
'/export/home/oracle/data/rman/backup/copycontrolfile.ctl';
release channel c1;
}
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Snapshot Control File:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
A copy of a database's control file taken by Recovery Manager. RMAN uses =
the snapshot control file to read a consistent version of a control file =
when either resynchronizing the recovery catalog or backing up the =
control file. A snapshot control file is created by Recovery Manager =
using the same Oracle code that creates backup control files: ALTER =
DATABASE BACKUP CONTROL FILE TO 'location'.=20
Determining the Snapshot Control File Location: When RMAN needs to =
resynchronize from a read-consistent version of the control file, it =
creates a temporary snapshot control file. The default name for the =
snapshot control file is port-specific. Use the set snapshot controlfile =
name command to change the name of the snapshot control file; subsequent =
snapshot control files that RMAN creates use the name specified in the =
command.=20
For example, start RMAN and then enter: set snapshot controlfile name = to '/oracle/dba/prod/snap_prod.ctl';
Chris Marquez
Oracle DBA
HEYMONitor=99 - heymonitor.com
"Oracle Monitoring & Alerting Solution"
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Feb 03 2005 - 15:06:16 CST
 |
 |