Question: Our rman catalog database is 188.8.131.52 right now, do I need to upgrade the database to 184.108.40.206 first, and then upgrade the catalog to 220.127.116.11?
The version of the RMAN catalog database does not need to match that of the recovery catalog. Therefore you can upgrade the RMAN catalog without upgrading the RMAN database. This is true of any version of the database, not only 12c.
If you are intending to upgrade the catalog schema to 12c then you need to run these 2 scripts:
If you are only upgrading the RMAN catalog, but not the database itself you’ll need to do this:
1. set your environment to a 18.104.22.168 $ORACLE_HOME.
2. connect to the RMAN catalog via an Oracle Net alias. For example:
$ sqlplus sys@RMANDEV as sysdba SQL*Plus: Release 22.214.171.124.0 Production on Wed Jan 21 10:44:26 2015 Copyright (c) 1982, 2014, Oracle. All rights reserved. Enter password: Connected to: Oracle Database 11g Enterprise Edition Release 126.96.36.199.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SYS@RMANDEV> SELECT name from v$database; NAME --------- RMANDEV SYS@RMANDEV> host echo $ORACLE_HOME /opt/app/oracle/product/12.1.0/db_1 SYS@RMANDEV> @$ORACLE_HOME/rdbms/admin/dbmsrmansys.sql alter session set "_ORACLE_SCRIPT" = true * ERROR at line 1: ORA-02248: invalid option for ALTER SESSION PL/SQL procedure successfully completed. PL/SQL procedure successfully completed. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. alter session set "_ORACLE_SCRIPT" = false * ERROR at line 1: ORA-02248: invalid option for ALTER SESSION
The ORA-02248 error can be ignored. This “_ORACLE_SCRIPT” is a 12c parameter and will only work in a 12c database.