How many people have received letters from Oracle that have stated that partitioning and / or Fine-grained auditing were turned on for Oracle 12C and they had to remove it otherwise pay a higher license fee or penalties. Well if you haven’t, your lucky as many customers have received this kind of letter, recently.
Well many have received the notice and then recompiled/de-installed the partitioning and/or fine grain auditing option on the databases that have contained a RMAN catalog user/schema.
When they removed the partition and/or the fine grain auditing and tried to upgrade the RMAN Catalog for the new Oracle 12c databases you will get this error:
Recovery Manager: Release 126.96.36.199.0 - Production on Thu May 26 13:08:02 2016 Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved. RMAN> connect catalog catalog_user/PW@Database; connected to recovery catalog database PL/SQL package catalog_user.DBMS_BA version 12.01.00.02 in RCVCAT database is too old RMAN> upgrade catalog recovery catalog owner is catalog_user enter UPGRADE CATALOG command again to confirm catalog upgrade RMAN> upgrade catalog error creating create_deleted_object_seq RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-06004: ORACLE error from recovery catalog database: ORA-00439: feature not enabled: Partitioning RMAN-06004: ORACLE error from recovery catalog database: ORA-00439: feature not enabled: Fine-grained access control RMAN>
Well if you have received this error, I hope you have a backup of the database, as this will corrupt you RMAN catalog. Well at least it corrupted our RMAN catalog and many others.
New RMAN catalog – Oracle 188.8.131.52 requires Partitioning, fine-grained auditing and other Enterprise edition options. Per Mike Dietrich’s BLOG, Going forward with Oracle 12c, you need to use Enterprise Edition for RMAN or Infrastructure databases:
“A separate single instance Oracle Database can be installed and used as an infrastructure repository for RMAN, Oracle Enterprise Manager Cloud Control, Automatic Workload Repository (AWR) Warehouse, Global Data Services Catalog, and Grid Infrastructure Management Repository without additional license requirements, provided that all the targets are correctly licensed. It may not be used or deployed for other uses.”
#1 – the RMAN catalog must be in its OWN Oracle 184.108.40.206 EE database – no other applications – Partitions need to be included
#2 – DBMS_LOB and UTTL_HTTP Must be present
#3 – Execute this script before upgrading the catalog: SQL> @$ORACLE_HOME/rdbms/admin/dbmsrmansys.sql
#4 – no Partitioning license required
#5 – Make sure you have a backup
#6 – p20432873_121020_Generic.zip – is a patch to fix the corrupted RMAN catalog due to Oracle 12c requirement – basically its a different recover.bsq script to fix the corruption. – This is only if its currently corrupted. One of the few bugs, that i was able to create an actually see a patch created for it – thank you Oracle.
#7 – See MOS Note:1927265.1 – this has more information
Please review Mike Dietrich’s Blog above regarding licenses and more information – https://blogs.oracle.com/UPGRADE/entry/rman_catalog_requires_ee_in
Hope this helps. Again, please backup your rman catalog before upgrading .