SOLUTION for rman error: RMAN-06429: RCVCAT database is not compatible with this version of RMAN

$ rman target / catalog rman/********@CATDB

Recovery Manager: Release 11.2.0.3.0 - Production on Sat Feb 14 18:05:00 2015

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database:XXX (DBID=607******5)
connected to recovery catalog database
recovery catalog is partially upgraded to 11.02.00.03

RMAN> crosscheck archivelog all;

ORACLE error from recovery catalog database: ORA-06550: line 1, column 41:
PLS-00201: identifier 'DBMS_RCVMAN.GETPACKAGEVERSION' must be declared
ORA-06550: line 1, column 34:
PL/SQL: Statement ignored

recovery catalog is partially upgraded to 11.02.00.03
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of crosscheck command at 02/14/2015 18:05:11
RMAN-12010: automatic channel allocation initialization failed
RMAN-06429: RCVCAT database is not compatible with this version of RMAN

This issue may appear from tape library backup log and also when connected to target and catalog to perform activities like take a backup or crosscheck archivelog...etc

The solution is simple.
While connected to both target and catalog on one of the database, run the below command and it will solve the issue:

$ rman target / catalog rman/*******@CATDB

Recovery Manager: Release 11.2.0.3.0 - Production on Sat Feb 14 18:59:43 2015

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: XXX (DBID=*********)
connected to recovery catalog database
recovery catalog is partially upgraded to 11.02.00.03

RMAN> UPGRADE CATALOG;

recovery catalog owner is RMAN
enter UPGRADE CATALOG command again to confirm catalog upgrade

RMAN> UPGRADE CATALOG;

recovery catalog upgraded to version 11.02.00.03
DBMS_RCVMAN package upgraded to version 11.02.00.03
DBMS_RCVCAT package upgraded to version 11.02.00.03

RMAN>

Comments

Post a Comment

Popular posts from this blog

How to resolve - ORA-09925: Unable to create audit trail file

When audit directory adump get filled, it prevents application from further connection and throw below error : ERROR: ORA-09925: Unable to create audit trail file Linux-x86_64 Error: 28: No space left on device Additional information: 9925 ORA-02002: error while writing to audit trail ORA-09925: Unable to create audit trail file Linux-x86_64 Error: 28: No space left on device Additional information: 9925 At this stage, as a DBA, you need to urgently resolve the issue because everyone will be calling that they cannot access the database. The first thing to do is to check if the file syste is filled up which might not show you 100% because is only the size defined for audit location is reached when you run df -h. However, the inode of the filesystem has reached 100% and that is why it cannot create further login audit files and so could not allow anyone login to the database until the space is freed. To find out if the inode is filled, run df -ih command on the linux syste
Read more
How to resolve error ORA-15032,ORA-15031,ORA-15025,ORA-15056 when adding a disk to asm. SQL> ALTER DISKGROUP ASM_FRA ADD DISK '/dev/dm-51'; ALTER DISKGROUP ASM_FRA ADD DISK '/dev/dm-51' * ERROR at line 1: ORA-15032: not all alterations performed ORA-15031: disk specification '/dev/dm-51' matches no disks ORA-15025: could not open disk "/dev/dm-51" ORA-15056: additional error message Linux-x86_64 Error: 13: Permission denied Additional information: 42 Additional information: 1927546192 I wanted to add  the following disk: (/dev/dm-51,/dev/dm-52,/dev/dm-53) First check the permissions on this files after the Unix admin has provision it. $ls -lrt /dev/dm* brw-rw---- 1 root disk 253, 19 Jan 31 13:46 /dev/dm-19 brw-rw---- 1 root disk 253, 53 Mar 2 21:04 /dev/dm-53 brw-rw---- 1 root disk 253, 52 Mar 2 21:04 /dev/dm-52 brw-rw---- 1 root disk 253, 51 Mar 2 21:04 /dev/dm-51 brw-rw---- 1 root disk 253, 46 Mar 2 21:12 /dev/dm-46 brw-r
Read more

How to repair a disk in a diskgroup

SUMMARY ======== "DG01" diskgroup cannot be mounted due to one disk member is missing: ====================================================== SQL> ALTER DISKGROUP DG01 MOUNT /* asm agent *//* {1:16801:2} */ NOTE: cache registered group DG01 number=1 incarn=0x2929b317 NOTE: cache began mount (first) of group DG01 number=1 incarn=0x2929b317 NOTE: Assigning number (1,1) to disk (/dev/asm-disk5) Sat Feb 14 06:41:49 2015 ERROR: no read quorum in group: required 1, found 0 disks NOTE: cache dismounting (clean) group 1/0x2929B317 (DG01) NOTE: messaging CKPT to quiesce pins Unix process pid: 7194, image: oracle@SLSLMEDIDBOP01 (TNS V1-V3) NOTE: dbwr not being msg'd to dismount NOTE: lgwr not being msg'd to dismount NOTE: cache dismounted group 1/0x2929B317 (DG01) NOTE: cache ending mount (fail) of group DG01 number=1 incarn=0x2929b317 NOTE: cache deleting context for group DG01 1/0x2929b317 GMON dismounting group 1 at 18 for pid 29, osid 7194 NOTE: Dis
Read more