RE: upgrade RMAN catalog problem
Date: Wed, 10 Dec 2008 19:22:51 -0600
Yes. There were two databases both 184.108.40.206.0 and both were upgraded with the pathset to 220.127.116.11.0 at the same time.
That is what I was thinking, just build a new catalog.
Date: Wed, 10 Dec 2008 16:44:15 -0800From: jkstill_at_gmail.comTo: joe_dba_at_hotmail.comSubject: Re: upgrade RMAN catalog problemCC: oracle-l_at_freelists.org On Mon, Dec 8, 2008 at 6:37 AM, Joe Smith <joe_dba_at_hotmail.com> wrote:
I have run into a problem with the patchset going from 18.104.22.168.0 to 22.214.171.124.0 on Red Hat 32bit x86 Linux. The two databases I upgraded worked fine. I can't upgrade my recovery catalog without getting the below error: connected to recovery catalog databasePL/SQL package RMAN.DBMS_RCVCAT version 11.01.00.06 in RCVCAT database is not currentDBGSQL: RCVCAT> begin :upgrade_completed := dbms_rcvcat.UPGRADE_COMPLETED;end; [11:02:40.057]DBGSQL: sqlcode = 6550 [11:02:40.057]Q: Are the only databases in that particular catalog the same databases that you upgraded from 126.96.36.199 to 188.8.131.52?If that is the case, why not just create a new catalog schema for the upgraded databases?You can't really use the old backups to restore to 184.108.40.206 databases to 220.127.116.11.Well, maybe you could, but it might be problematic.Something to consider anyway. Leave the old catalog as is, create a new one, register the upgradeddatabases in the new catalog.Should you need to restore from the old backups, you will need to use 18.104.22.168Jared StillCertifiable Oracle DBA and Part Time Perl Evangelist
Send e-mail anywhere. No map, no compass. http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_anywhere_122008 Received on Wed Dec 10 2008 - 19:22:51 CST