This thread highlights the importance of building and using a test system for RMAN backups and recoveries. There are few things more important that being able to recover a database. For a DBA, that is probably the single most important item to be sure of. On Dec 27, 2007 6:26 AM, <krish.hariharan@xxxxxxxxxxxx> wrote: > It would be prudent to test the recovery given this change. While this > depends on how you test recoveries, one easy way is to create a dummy > tablespace in production, have it backed up as you normally would and then > recover a file of this dummy tablespace with a roll forward. > > > > -Krish > > > ------------------------------ > > *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto: > oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Shastry(DBA) > *Sent:* Thursday, December 27, 2007 6:34 AM > *To:* Mercadante, Thomas F (LABOR) > *Cc:* oracle-l > *Subject:* Re: How to UPGRADE CATALOG in RMAN after post release upgrade? > > > > Hi all, > > Thanks for your immediate responses and help, I really Thank for all the > gurus who are giving valuable suggestions and guidelines. > > We took a risk in upgrading the catalog, as Peter suggested the upgrade > went, but with few errors as some RMAN backups were running during the > upgrade process. > > we saw many RMAN error alerts later and resubmitted and it is going fine. > Let me know if i have more suggestions on this. > > Thanks a ton, > Ananth > > On Dec 27, 2007 6:44 PM, Mercadante, Thomas F (LABOR) < > Thomas.Mercadante@xxxxxxxxxxxxxxxxx> wrote: > > Ananth, > > > > My guess is that you would run the Rman executable out of the 10.2.0.3Oracle > home connecting to the existing catalog, and then issue the UPGRADE > CATALOG command. But that is just a guess. > > > > A caution though - if you do this, your existing Rman backups for other > 10.2.0.1 databases may not work. You need to test this! > > > > I would test by creating a new 10.2.0.3 rman catalog and registering some > of the older databases in it. If they register ok, then you should not have > a problem, and you could go ahead and upgrade your existing catalog. > > > > You will probably be ok. The Rman catalog is pretty stable - no changes > between releases (especially between the releases that you are going thru). > We are running two rman catalogs (9.2.0.7 & 10.2.0.2) in a 9.2.0.7database > with no problems at all. > > > > Good Luck! > > > > Tom > > > ------------------------------ > > *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto: > oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Shastry(DBA) > *Sent:* Thursday, December 27, 2007 7:35 AM > *To:* oracle-l > *Subject:* How to UPGRADE CATALOG in RMAN after post release upgrade? > > Hi Gurus, > > We have upgraded the PROD from 10.2.01 to 10.2.0.3 and we are at the stage > where oracel is asking for RMAN catalog upgrade as we are using RMAN for > backup purpose > How to do this basically? > If we do Catalog upgrade,Will this affect to other RMAN backups? > > we are using common catalog for many prod databases backup. > > I am looking for some light...like whether can we upgrade and how to do > so.... > > Will this affect other RMAN backups? > > But I see the Oracle upgrade readme says the below information, but > doesn't say how to do it exactly. > > If you are using the Oracle Recovery Manager catalog, enter the following > command: > > $ rman catalog username/password@alias > RMAN> UPGRADE CATALOG; If you are using the Oracle Recovery Manager > catalog, enter the following command: > > $ rman catalog username/password@alias > RMAN> UPGRADE CATALOG; > > Can anyone please help me out on this as I am not aware much on RMAN? > > Thanks, > Ananth > > > > > > > -- Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist