FAQ
I have run into a problem with the patchset going from 11.1.0.6.0 to 11.1.0.7.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 current

DBGSQL: RCVCAT> begin :upgrade_completed := dbms_rcvcat.UPGRADE_COMPLETED;end; [11:02:40.057]DBGSQL: sqlcode = 6550 [11:02:40.057]DBGSQL: B :upgrade_completed = 0RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-00554: initialization of internal recovery manager package failedRMAN-00600: internal error, arguments [9302] [6550] [begin :upgrade_completed := dbms_rcvcat.UPGRADE_COMPLETED;end; ] [] []RMAN-06004: ORACLE error from recovery catalog database: ORA-06550: line 1, column 44:PLS-00302: component 'UPGRADE_COMPLETED' must be declaredORA-06550: line 1, column 10:PL/SQL: Statement ignored

If I run the below sql

select * from rcver;
VERSION------------11.01.00.06


Every time I try to connect and run UPGRADE CATALOG I get the error.
Has anybody seen this before?

Send e-mail faster without improving your typing skills.
http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_speed_122008

Search Discussions

  • Finn Jorgensen at Dec 8, 2008 at 9:26 pm
    You're not alone :

    https://metalink2.oracle.com/metalink/plsql/f?p=130:15:8716035823550018504::::p15_database_id,p15_docid,p15_show_header,p15_show_help,p15_black_frame,p15_font:BUG,7431720,1,1,1,helvetica

    https://metalink2.oracle.com/metalink/plsql/f?p=130:15:8716035823550018504::::p15_database_id,p15_docid,p15_show_header,p15_show_help,p15_black_frame,p15_font:BUG,7517996,1,1,1,helvetica

    Finn
    On Mon, Dec 8, 2008 at 9:37 AM, Joe Smith wrote:

    I have run into a problem with the patchset going from 11.1.0.6.0 to
    11.1.0.7.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:
    Every time I try to connect and run UPGRADE CATALOG I get the error.
    Has anybody seen this before?


    ------------------------------
    Send e-mail faster without improving your typing skills. Get your Hotmail(R)
    account.<http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_speed_122008>
    --
    http://www.freelists.org/webpage/oracle-l
  • Joe Smith at Dec 8, 2008 at 10:02 pm
    Thanks Finn. That is useful information. Do you think they are going to write a patch for the error?


    thanks.



    Date: Mon, 8 Dec 2008 16:26:35 -0500From: finn.oracledba_at_gmail.comksTo: joe_dba_at_hotmail.comSubject: Re: upgrade RMAN catalog problemCC: oracle-l_at_freelists.org
    You're not alone :


    https://metalink2.oracle.com/metalink/plsql/f?p=130:15:8716035823550018504::::p15_database_id,p15_docid,p15_show_header,p15_show_help,p15_black_frame,p15_font:BUG,7431720,1,1,1,helvetica


    https://metalink2.oracle.com/metalink/plsql/f?p=130:15:8716035823550018504::::p15_database_id,p15_docid,p15_show_header,p15_show_help,p15_black_frame,p15_font:BUG,7517996,1,1,1,helvetica


    Finn
    On Mon, Dec 8, 2008 at 9:37 AM, Joe Smith wrote:

    I have run into a problem with the patchset going from 11.1.0.6.0 to 11.1.0.7.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:


    Every time I try to connect and run UPGRADE CATALOG I get the error.Has anybody seen this before?

    Send e-mail faster without improving your typing skills. Get your Hotmail® account.

    Suspicious message? There’s an alert for that.
    http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_broad2_122008
  • Finn Jorgensen at Dec 9, 2008 at 1:19 am
    One would think so, but the best way is to open your own SR and get the word
    straight from Oracle. The first one was logged about 3 months ago so
    something should be coming up.

    Finn
    On Mon, Dec 8, 2008 at 5:02 PM, Joe Smith wrote:

    Thanks Finn. That is useful information. Do you think they are going to
    write a patch for the error?

    thanks.
    --
    http://www.freelists.org/webpage/oracle-l
  • Jared Still at Dec 11, 2008 at 12:44 am

    On Mon, Dec 8, 2008 at 6:37 AM, Joe Smith wrote:

    I have run into a problem with the patchset going from 11.1.0.6.0 to
    11.1.0.7.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 11.1.0.6 to 11.1.0.7?

    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 11.1.0.6 databases to
    11.1.0.7.

    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
    11.1.0.6

    Jared Still
    Certifiable Oracle DBA and Part Time Perl Evangelist
  • Joe Smith at Dec 11, 2008 at 1:22 am
    Yes. There were two databases both 11.1.0.6.0 and both were upgraded with the pathset to 11.1.0.7.0 at the same time.


    That is what I was thinking, just build a new catalog.


    thanks.


    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 wrote:

    I have run into a problem with the patchset going from 11.1.0.6.0 to 11.1.0.7.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 11.1.0.6 to 11.1.0.7?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 11.1.0.6 databases to 11.1.0.7.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 11.1.0.6Jared 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
  • Mark W. Farnham at Dec 11, 2008 at 2:48 am
    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.



    mwf



    From: 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
    Cc: oracle-l_at_freelists.org
    Subject: Re: upgrade RMAN catalog problem



    On Mon, Dec 8, 2008 at 6:37 AM, Joe Smith wrote:

    I have run into a problem with the patchset going from 11.1.0.6.0 to
    11.1.0.7.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 11.1.0.6 to 11.1.0.7?

    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 11.1.0.6 databases to
    11.1.0.7.

    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
    11.1.0.6

    Jared Still
    Certifiable Oracle DBA and Part Time Perl Evangelist

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouporacle-l @
categoriesoracle
postedDec 8, '08 at 2:37p
activeDec 11, '08 at 2:48a
posts7
users4
websiteoracle.com

People

Translate

site design / logo © 2022 Grokbase