RE: upgrade RMAN catalog problem
Date: Wed, 10 Dec 2008 21:48:44 -0500
I think you're right Jared, but it points out an interesting challenge for very large databases that can rarely stand the overhead of a full backup and which rely on a base laid down and "merged" incrementals.
I think the sum of what you're related means you need to upgrade immediately prior to a window where you are allowed to make a full backup. Yet another "rolling upgrade" constraint to live within.
Thanks for the analysis.
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
On Behalf Of Jared Still
Sent: Wednesday, December 10, 2008 7:44 PM To: joe_dba_at_hotmail.com
Subject: Re: upgrade RMAN catalog problem
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 database
PL/SQL package RMAN.DBMS_RCVCAT version 11.01.00.06 in RCVCAT database is not current
DBGSQL: 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 upgraded
databases in the new catalog.
Should you need to restore from the old backups, you will need to use 18.104.22.168
Certifiable Oracle DBA and Part Time Perl Evangelist