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 backup generates traces in Oracle 12.2.0.1

Oracle 12.2.0.1 seems to be the “tracing” release without further patch or parameter treatments. After posting about MMON unconditional traces in Oracle 12.2.0.1 a day ago, I received a couple of comments either on the blog, via LinkedIn or Twitter regarding other trace facilities in Oracle Database 12.2.0.1. One of them is the case that RMAN backup generates traces in Oracle 12.2.0.1. And please, very important upfront: Oracle Database 12.2.0.1 is a very stable and reliable release based on all the customer feedback Roy and I received so far. For instance, when we check for optimizer issues causing trouble in…

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…

DBUA and Read-Only Tablespaces – Things to Know II

Related Blog Posts: DBUA and Read-Only Tablespaces – Things to Know – I (Feb 3, 2016) DBUA and Read Only Tablespaces – Things to Know – II (Mar 30, 2016) DBUA displays wrong RMAN Backup for Restore (Sep 21, 2015) DBUA 12c and “datapatch.pl” – things to know (Jul 20, 2015) Thanks to Rodolfo Baselli commenting on a previous blog post about the DBUA and Read-Only Tablespaces I dug a bit deeper and found out that “assuming silently” does not mean “works as intended“. But one piece after another. Rodolfo commented that if he triggers the DBUA to switch all data…

DBUA and Read-Only Tablespaces – Things to Know – I

Related Blog Posts: DBUA and Read-Only Tablespaces – Things to Know – I (Feb 3, 2016) DBUA and Read Only Tablespaces – Things to Know – II (Mar 30, 2016) DBUA displays wrong RMAN Backup for Restore (Sep 21, 2015) DBUA 12c and “datapatch.pl” – things to know (Jul 20, 2015) Some people prefer the manual upgrade on the command line, others prefer the graphical tool Database Upgrade Assistant (DBUA). DBUA and Read-Only Tablespaces  The DBUA offers you an option of setting your non-Oracle tablespaces read-only during the upgrade. What the option doesn’t tell you is the purpose – and…

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

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…

Fundamental Oracle flaw revealed??? Update …!

Writing a blog has a nice effect on the side: it brings me in touch with people I’ve never met – but we have similar targets or interests. Today I’ve received a comment from Gökhan Atil about the Fundamental Oracle Flaw known also as the SCN issue. And for sure I did visit Gökhan’s blog and I did watch his very interesting 5 minutes demonstration how to bring down a database with the SCN issue. Which is very good to know as I thought the database won’t come down because of this issue. But watch Gökhan’s video by yourself and…

Fundamental Oracle flaw revealed??? Really …?

This Infoworld article from Jan 17, 2012  Fundamental Oracle flaw revealed did alert Oracle database customers.Infoworld has raised this issue to Oracle before going public with it. Patches are included in the Jan 2012 CPU and PSU. So again, it’s strongly recommended to apply the Jan 2012 PSU (or CPU if you are just asking for security fixes) to your environments. Please read on OTN the Critical Patch Update Advisory from January 2012 You’ll find an explanation from Oracle Support in MOS Note:1376995.1: Information on the System Change Number (SCN) and how it is used in the Oracle Database What…