RMAN Backup Gives RMAN-06091: No Channel Allocated for Maintenance

I really don’t want to turn this blog into an accumulation of issues and flaws. But as I explained many times before, the blog for me is also a way to dump information I likely will need the sooner or later again. Recently I blogged about another RMAN issue in Oracle 12.2.0.1 with traces. This was fixed with the July 2018 RU for Oracle 12.2.0.1. But the issue below about which Piero Ferraz from Brazil alerted me (thanks!!!), happens in exactly this RU. RMAN Backup Gives RMAN-06091: No Channel Allocated for Maintenance This issue gets introduced with the July 2018…

ZDLRA ready for Oracle Database 18c

ZDLRA is one of the best acronyms ever. It took me 5+ years to not mix up the sequence of characters 🙂 And even Larry made a joke about the name a while ago at his OOW keynote (I think it was 2016). ZDLRA stands for Zero Data Loss Recovery Appliance. And that basically tells you what it is. Hence, it isn’t a bad acronym as it tells you straight forward what it does. Good news: ZDLRA ready for Oracle Database 18c. ZDLRA ready for Oracle Database 18c Why am I writing about this? Some of the customers I’m working…

RMAN Recovery Catalog with July PSU: How to resolve RASCHEMAVER and BASCHEMAVER schema mismatch

Related blog posts: RMAN Catalog Upgrade fails – ORA-02296 – error creating modify_ts_pdbinc_key_not_null (April 19, 2016) RMAN Catalog requires Enterprise Edition (EE) since Oracle Database 12.1.0.2 (April 22, 2016) RMAN Catalog Upgrade to Oracle 12.1.0.2 (August 1, 2014) Thanks to Ah Huat Tan from Amway IT Services for keeping me updated! Actually as I see that more people who got hit by this issue so I’d consider it to be worth to write about it. Problem and Analysis You’d apply the July 2016 PSU or BP. According to the readme you are required to upgrade your RMAN catalog afterwards. The…

MOS Note:136697.1 – New HCHECK.SQL for Oracle Database 12c

A while back we added this slide to our big slide deck: The story behind this slide A large and important customer in the US tested a patch set upgrade – but when they approached the production upgrade from 11.2.0.2 to 11.2.0.3 on a large RAC cluster they’ve had to cancel the attempt and revert to the previous state. Reason They’ve hit a dictionary corruption somewhere silently sleeping in the database causing no trouble at all so far – until the upgrade touched the broken structures They’ve asked us: “How could we ensure the database is really healthy and in…

RMAN Catalog Upgrade fails – ORA-02296 – error creating modify_ts_pdbinc_key_not_null

This issue got raised to my via a customer I know for quite a while – all credits go to Andy Kielhorn for digging down into that issue and solving it. Failed RMAN Catalog Upgrade from 11.2.0.4 to 12.1.0.2 The RMAN catalog upgrade: SQL> @?/rdbms/admin/dbmsrmansys.sql $ rman CATALOG rman/xxx@rman01 RMAN> UPGRADE CATALOG; RMAN> UPGRADE CATALOG; failed with the following sequence of error messages: error creating modify_ts_pdbinc_key_not_null RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-06004: ORACLE error from recovery catalog database: ORA-02296: cannot enable (RMAN.) – null values found error creating modify_tsatt_pdbinc_key_not_null RMAN-00571: =========================================================== RMAN-00569: =============== ERROR…

RMAN NOOPEN Clause DUPLICATE FOR UPGRADE

In Oracle Database 12c, the RMAN “DUPLICATE” command has new “NOOPEN” option which clones the database but does not open the auxiliary instance. This feature can be used to duplicate a database to higher version. MOS Note: 2022820.1 Upgrade to 12c database using RMAN Duplicate with NOOPEN clause The note contains also a full example on how to duplicate the production database as a standby, and upgrade it. –Mike

Migration IBM AIX ==> SPARC Solaris with Data Guard

Can we migrate our database with Oracle Data Guard? We are getting this question asked quite often during our workshops or via email. And if you are staying within the same operating system family (such as Red Hat 5.8 to OL 7) all is fine, and this is one of the best and most simple approaches to jump between servers. Even when you add a subsequent database upgrade all is very straight forward. But what if you mix operating systems? The Support Note for Heterogeneous Data Guard Configurations explains which combinations are allowed beginning with specific releases: MOS Note: 413484.1 Data Guard Support…

RMAN Catalog requires Enterprise Edition (EE)
since Oracle Database 12.1.0.2

Credits go to Cameron Hodge, Malcom and Martin Mäs who all highlighted issues to me following my previous entry about RMAN – and sorry for any disappointment but I wasn’t aware of all these nice little things. Ok, you’d upgrade your RMAN Catalog to be ready to backup/recover Oracle Database 12.1.0.2 databases and you see this error: 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 Now you start to wonder as your Catalog Database had been an Oracle Standard…

RMAN Catalog Upgrade to Oracle 12.1.0.2

It sounds so simple – but in this specific case a bit of doc reading is required as upgrading the RMAN catalog to handle Oracle 12.1.0.2 databases is not as trivial as in the past. Thanks to a German customer and a friendly colleague from Sales Consulting in Stuttgart I have learned my RMAN lesson for Oracle Database 12.1.0.2 this week. A simple “upgrade catalog” is not the correct step once you’d like to handle backups of Oracle 12.1.0.2 databases in your current catalog schema.  Even though you may not have ever heard before about Virtual Private Catalogs you need…