Different software components (operating systems, databases, etc.) are updating our clocks automatically when our country changes the clock (when daylight saving starts or ends). In order to do that, the system has to know the date for the daylight saving. This is the DST information.
I had a bad night last Thursday.
After patching two test RAC databases and one production RAC with 180417 DB Bundle Patch (and some one-offs), I got to the point where it was time to update the most critical RAC system.
We were really looking forward to this as we had hit a few bugs that this DBBP and one-offs should fix. But boy, did that go wrong…
Lately I started patching a client’s database (184.108.40.206) to the latest PSU (180417). This is a RAC environment with streams and all kind of other features, so over the time we hit quite a lot of different bugs. When we planned this PSU (we installed the bundle patch version), we added about 7 one-off patches (some are recommended by Oracle and some we had to add because the bugs affected us quite badly).
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 220.127.116.11 home, for other versions the steps might be a bit different.
In February ’17 I participated in Mike Dietrich’s upgrade workshop and it was great! I don’t want to repeat stuff that he said there, you can read everything on his blog. This workshop made me think about upgrades I did in the past (and I did quite a few) and important things to think about before and after upgrading a database.