RMAN connect error - db reporting incompatible target version - oracle

Question

I'm trying to use RMAN to backup an Oracle database without a backup catalog. When attempting to connect to the target database I'm getting an error message that my RMAN version is incompatible with my database version. This seems odd to me as my RMAN version is 11.2.0.1 and my database version is 11.2.0.3 but the RMAN error states that I need to use RMAN 8.0.4.0 to 11.1.0.7. Why is my database reporting version 11.1.0.7 to RMAN when it should be reporting as 11.2.0.3?
C:\>rman
Recovery Manager: Release 11.2.0.1.0 - Production on Tue May 24 09:48:07 2016
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN> connect target SYS/oracle#tnsname
Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 11.1.0.7 req
uired
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06429: TARGET database is not compatible with this version of RMAN
RMAN> exit
Recovery Manager complete.
C:\>sqlplus SYS/oracle#tnsname
SQL*Plus: Release 11.2.0.1.0 Production on Tue May 24 09:49:24 2016
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select * from v$version;
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
PL/SQL Release 11.2.0.3.0 - Production
CORE 11.2.0.3.0 Production
TNS for 32-bit Windows: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
SQL>

Answer 1

You need to change the compatible initialisation parameter to 11.2.0 (or higher). You can do that with alter system:
ALTER SYSTEM SET COMPATIBLE = '11.2.0' SCOPE = SPFILE;
The change won't take effect until you restart the database. If you don't have a server parameter file for some reason then you can change it in the pfile instead, but you still need to bounce the database to pick up the change.
Make sure you understand the setting and its implications, from the upgrade guide and admin guide. It sounds like it was just missed after upgrading from 11gR1, but if you can make sure it wasn't left on the old version for a reason before changing it.

Answer 2

My problem was due to an incomplete upgrade. Apparently not all of the catalog update scripts were executed properly. Here's what fixed it for me:
SQLPLUS /nolog
SQL> CONNECT / AS SYSDBA
SQL> #?/rdbms/admin/dbmsrman.sql
SQL> #?/rdbms/admin/prvtrmns.plb
SQL> #?/rdbms/admin/dbmsbkrs.sql
SQL> #?/rdbms/admin/prvtbkrs.plb

Answer 3

Error
While connecting with RMAN Command window getting the following errors:
RMAN-06438: error executing package DBMS_RCVMAN in TARGET database
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN
Cause
“SYS.DBMS_RCVMAN” package has error which causing the problem. May be package is in-valid state.
Solution
We tried to check in target database if it’s invalid.
select OWNER, STATUS, substr(OBJECT_NAME,1,40), OBJECT_TYPE from DBA_OBJECTS where OBJECT_NAME IN ('DBMS_RCVMAN', 'DBMS_BACKUP_RESTORE' ) ;
Try to recompile it and check the status.
#$ORACLE_HOME/rdbms/admin/utlrp.sql
If 2nd steps is not working the package is not become valid, then try to re-create the package by executing following steps from SYS user.
#?/rdbms/admin/dbmsrman.sql
#?/rdbms/admin/prvtrmns.plb