This week I worked on a messy patch. I have a RAC environment with 22.214.171.124 and an old PSU and all kind of one-off patches and I wanted to install the latest PSU (180417). It sounds simple, but it’s not so simple. The thing is that I have 4 database running from the same ORACLE_HOME, all of them are RAC, while some of them are stand-alone, some are primary for standby located on a different RAC and some are standby for a primary located on a different RAC. And the problem with that is that you cannot install a PSU on the primary first, either together or patch the standby first.
I’ve installed quite a few PSUs in my professional life, but this time, it was something else. I’m talking about a RAC environment with 2 nodes and a database containing JVM, so this was a complex patch to begin with. The problem is the the readme is incomplete and on top of that I ran into a few issues (some I could find on MOS but some I couldn’t). I’m writing this to assist anyone who needs to install this patch by providing the steps that worked for me. Please note that I patched 126.96.36.199 home, for other versions the steps might be a bit different.
When Oracle releases a new version or even a petchset, sometimes they change the default value of initialization parameters or add new features and introducing new parameters with them. These changes affect the behavior of many components. In this post I’d like to address how I deal with parameter of features changing optimizer behavior. Continue reading
As of Nov 2015, Oracle decided to change the naming method for PSU (Patch Set Update).
Lately, I talked to several customers about Oracle patches, and each time it takes me quite a while to explain how it works.
So for all of you who don’t know about the different patching options (and what’s new in 12c), here is a short explanation about the topic.