From oracle-l-bounce@freelists.org Thu Feb 3 15:06:16 2005 Return-Path: Received: from air891.startdedicated.com (root@localhost) by orafaq.com (8.12.10/8.12.10) with ESMTP id j13L6GMq000617 for ; Thu, 3 Feb 2005 15:06:16 -0600 X-ClientAddr: 206.53.239.180 Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180]) by air891.startdedicated.com (8.12.10/8.12.10) with ESMTP id j13L6Eem000607 for ; Thu, 3 Feb 2005 15:06:14 -0600 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id A83DB6D1B5; Thu, 3 Feb 2005 15:05:17 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15913-06; Thu, 3 Feb 2005 15:05:17 -0500 (EST) Received: from turing (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 25C9D6D1BB; Thu, 3 Feb 2005 15:05:17 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-type: text/plain; charset=Windows-1252 Content-Transfer-Encoding: 8bit Subject: RE: Diff between...CONTROLFILE: AUTOBACKUP / include current / backup current / copy current / Snapshot Date: Thu, 3 Feb 2005 15:02:30 -0500 Message-ID: <7E412C164E6ECB468834A39F31E6E0D406689040@mbs06dc.na.aarp.int> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Diff between "controlfile autobackup" and "snapshot controlfile" Thread-Index: AcUJbaYVqw8+SqKBTKib3Z7SAZTJ+wAuwkYdAACBUiE= From: "Marquez, Chris" To: , "Oracle L (E-mail)" X-OriginalArrivalTime: 03 Feb 2005 20:02:31.0233 (UTC) FILETIME=[4B40B310:01C50A2B] X-archive-position: 15768 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-To: oracle-l-bounce@freelists.org X-original-sender: CMarquez@aarp.org Precedence: normal Reply-To: CMarquez@aarp.org X-list: oracle-l X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at avenirtech.net X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on air891.startdedicated.com X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,LINES_OF_YELLING autolearn=ham version=2.60 X-Spam-Level: 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. -------------------------------------------- CONTROLFILES - BACKUP vs. COPY -------------------------------------------- =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 backup 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 RMAN backupset containing the current = controlfile. 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-l