“The software home is already registered in the central inventory ?” A failed attempt to apply RU on 19c Grid Infrastructure home before it is configured

I recently came accross a new (to me) error when trying to upgrade Grid Infrastructure on my lab, a 2-node 18.6 RAC cluster. To upgrade Grid Infrastructure directly to 19c with the latest Release Update 19.4, I downloaded the 19.3 base release and tried to apply RU 19.4 before launching the upgrade : (Please refer […]

Read More

Exadata Cloud at Customer : Drill down into Cloud Tooling RPM content

On one of my Exadata Cloud at Customer system, I recently had an issue which required to check exactly which files were updated when upgrading the cloud-specific tooling included on Exadata Cloud at Customer, also know as dbaastools_exa. I needed to know if a configuration file had been overwritten or not, when upgrading dbaastools_exa. My […]

Read More

Exadata Cloud at Customer : Grid Infrastructure patch under the hood

Following up with this blog post, here is a quick overview of what is performed on Exadata Cloud at Customer nodes when a Grid Infrastructure patching is launched via the web interface, the Oracle Cloud control plane. The whole patch process is not that different from the precheck process. Most of the steps are similar, […]

Read More

Exadata Cloud at Customer : Grid Infrastructure patch precheck under the hood

I am now exploring the brand new Grid Infrastructure patching method for Exadata Cloud at Customer. With Exadata Cloud at Customer version 18.1.4.4, it is now possible to patch Grid Infrastructure with a few clicks in the GUI. Let’s see exactly which steps are performed. First, with my preferred method (CLI 🙂 ), I run […]

Read More

Problem with datapatch, sqlpatch_bootstrap.sql and obj$

(Picture by Hermes Rivera, via Unsplash) EDIT : This bug has finally been fixed by patch 28809007 and should be included with release 20.1 🙂 ! This blog post describes a very specific problem I encountered while using datapatch. I recently patched 400+ 12.1.0.2 databases on RHEL 7.5 with Database Proactive Bundle Patch + OJVM […]

Read More

Patch 22652097 in 12.1 makes optimizer_adaptive_features parameter obsolete

After having several issues with adaptive features on 12.1 databases, in some cases, the quickest way to solve problems was to simply set ‘optimizer_adaptive_features’ parameter to FALSE. In 12.2, this parameter became obsolete and was replaced with two different parameters : ‘optimizer_adaptive_plans’ and ‘optimizer_adaptive_statistics’. Therefore, it is recommended to apply Patch 22652097 (PROVIDE SEPARATE CONTROLS […]

Read More