RMAN Upgrade – ORA-00439: feature not enabled…

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 12.1.0.2.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.

ISSUE:

New RMAN catalog – Oracle 12.1.0.2 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.”

https://blogs.oracle.com/UPGRADE/entry/rman_catalog_requires_ee_in

SOLUTION:

#1 – the RMAN catalog must be in its OWN Oracle 12.1.0.2 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 .

MOUS15 is here !!!

If you are in the Indiana, Michigan, Illinois, Ohio or Canada region and want to see and experience great Oracle user and technical presentations, networking and hands-on workshops, please register to the Michigan Oracle User Summit (#MOUS15), on Wednesday, November 18th at Schoolcraft college in Livonia, Michigan (www.mous.us).    Its a full day of presentations (45) that include Big Data presentations, Hyperion presentations, JDEdwards, Oracle Applications, Middleware (SOA), Database (Oracle12c, RAC, others) and 2 hands-on workshops – #cloneattack and #racattack.   We also have 13 Oracle Ace and Ace directors, Rich Niemiec of Rolta will be our keynote speaker.   Please visit our website (www.mous.us) or guidebook for more details on the conference content.

So not only do you get some great user and technical presentations, but you get 2 great hands-on workshops – Clone Attack and Racattack (www.racattack.org).

Clone attack (www.delphix.com ) – did you ever want to create development databases from production with a small footprint and dynamic way ?   Well come to MOUS15 and create many development databases on your own PC.

RACATTACK – (www.racattack.org) – Racattack allows you to create a 12c RAC database on your own PC, yes, you too can have your own RAC database on your pc.

Wait there is more !! – WE ARE ON GUIDEBOOK – http://www.guidebook.com (Look for MOUS) its free !!

Lastly, this conference is a great way to network with other Oracle users, a full day of presentations, hands-on workshops, great food , education and its priced reasonably ($50 pre-register, $75 at door).

Hope to see you at the conference and please contact me with any questions,

--Mike Gangler
mjgangler@yahoo.com

RMAN-03009 Error with ORA-19511

I recently modified the RMAN servers to perform auto backup of the controlfiles, etc. After the change, the incremental’s worked without error.

When I Ran the Full RMAN backup, got the following errors :
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ch00 channel at 08/03/2014 18:42:51
ORA-19506: failed to create sequential file, name=”c-2369888563-20140803-ff”, parms=””
ORA-27027: sbtremove2 returned error
ORA-19511: Error received from media manager layer, error text:
Failed to remove, c-2369888563-20140803-ff, from image catalog.

The reason why is the rman backups were NOT using the rman catalog for over a year (Commented out for some odd reason). The RMAN backups were running but without a catalog connection.

So when i added control file auto backup, I received this error.

To FIX:

Connect to RMAN using the rman catalog
run : rman> crosscheck archivelog all;
Run Full backup.

Once the crosscheck cleaned up all the archive logs since 2013, the full backup could be performed.

I also added the RMAN catalog to all the backups on this machine