DBAsupport.com Forums - Powered by vBulletin
Results 1 to 5 of 5

Thread: RMAN: CREATE CATALOG fails

  1. #1
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092

    Question

    I am trying to create an 8.1.7 RMAN catalog on a 9.0.1.2 database. I have done this without a problem on several 9.0.1.0 database, but this is my first time on the patched version.

    I have a catalog owner, rman817. rman817 has been granted connect, resource, dba, and recovery_catalog_owner. When I try to create the catalog, I get an error message:
    Code:
    oracle8@oradev3 dev817$ rman catalog rman817/rman817@rcvcat.us 
    
    Recovery Manager: Release 8.1.7.0.0 - Production
    RMAN-06008: connected to recovery catalog database
    RMAN-06428: recovery catalog is not installed
    
    RMAN> create catalog tablespace "RMAN817_DATA";
    RMAN-06444: dbms_rcvman package body created with compilation errors
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-06433: error installing recovery catalog
    When I go in to check the package in question, I get:
    Code:
    SQL> alter package dbms_rcvman compile body;
    Warning: Package Body altered with compilation errors.
    SQL> show errors package body dbms_rcvman;
    Errors for PACKAGE BODY DBMS_RCVMAN:
    
    LINE/COL ERROR
    -------- -----------------------------------------------------------------
    6624/4	 PLS-00593: default value of parameter "AVAILABLE" in body must
    	 match that of spec
    
    6625/4	 PLS-00593: default value of parameter "UNAVAILABLE" in body must
    	 match that of spec
    
    6626/4	 PLS-00593: default value of parameter "EXPIRED" in body must
    	 match that of spec
    
    6753/4	 PLS-00593: default value of parameter "PIECECOUNT" in body must
    	 match that of spec
    Anybody got any hints?
    Jeff Hunter

  2. #2
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    Just heard from Oracle Support: Bug 1645903. The workaround is to:
    alter system set events '10932 trace name context level 32768';
    Jeff Hunter

  3. #3
    Join Date
    Oct 2000
    Location
    Saskatoon, SK, Canada
    Posts
    3,925
    Jeff,

    Just curious what is the DB 8.1.7 version and platform. I just heard from oracle that 8.1.7.3 patchset is out. But curious to know whether this was with this patchset? Did you try upgrade the catalog?

    NOTE: AFAIK, you have to set the RMAN in backward compatibility mode and not forward. In your case the catalog seems to reside on the 8.1.7 where as the db is 9i. Did you try vice-versa. I'm sure that the vice-versa would work.


    I'm interested in keeping track of the proceedings of this issue.


    Thanx,
    Sam

    [Edited by sambavan on 01-15-2002 at 02:47 PM]
    Thanx
    Sam



    Life is a journey, not a destination!


  4. #4
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    Both the recovery catalog and the source database were on solaris. I tried the 8.1.7 database with 8.1.7.0 and 8.1.7.2.

    The catalog was an 8.1.7 catalog on a 9.0.1.2 database. Since everything was owned by rman817, I shouldn't have a problem.

    I have been looking for that 8.1.7.3 patchset, but haven't found it on the ftp site or metalink. I hope it comes out soon.
    Jeff Hunter

  5. #5
    Join Date
    Jun 2001
    Location
    Helsinki. Finland
    Posts
    3,938

    I have been looking for that 8.1.7.3 patchset, but haven't found it on the ftp site or metalink. I hope it comes out soon.
    Jeff, it will be available on January 18th.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width