What happened so far on my Journey to the Cloud?
- Part I – Push a Button (Dec 3, 2015)
- Part II – Switch On/Off and Remove (Dec 4, 2015)
- Part III – Patch, patch, patch (Dec 22, 2015)
- Part IV – Clean Up APEX (Jan 19, 2016)
- Part V – TDE is wonderful (Jan 28, 2016)
- You are here ==> Part VI – Patching does not work (Apr 18, 2016)
- Part VII – APEX is in CDB$ROOT again (Dec 21, 2016)
Patching in the Cloud
I would like to patch my Oracle DBaaS Cloud today. It was so simple a few weeks ago. But I didn’t patch it yet up to the January 2016 PSU (220.127.116.11.160119PSU) – shame on me 🙁
Please don’t be scared by the weird mix of German and English – I filed a bug for this months ago … and maybe one magic sunny day I can switch the language back to pure English …
Anyhow, I choose my VM and it highlighted to me an available patch to apply, the January 2016 PSU:
Let’s do the PreCheck
I chose PRECHECK first from the drop-down hamburger menu to the right and received the following message:
But where are the logs? There is no link, no hint, nothing.
Let’s check the README
At this point I decided to check the README to find out whether I missed something important. So I clicked on README and received this meaningful message:
Potentially not a fault of the Cloud folks as I realized by myself that the MOS facility to link patches directly is broken since weeks. A manual interaction in MOS to locate the README is necessary – but it gave me no indication regarding the above failed precheck.
Force to apply the PSU
Next step: FORCE to apply the patch (2nd option in the hamburger menu). But again the result is not positive showing me again a weird mix of Denglish (Deutsch and English).
Well, that is somewhat unexpected. I checked with some people who are way more familiar than I with our DBaaS Cloud after consulting our documentation and googling around – and learned that this functionality is broken since several weeks,
No further comment necessary.