Tomorrow we’ll start our new Virtual Classroom Web Seminar Series, this time for the Americas in a convenient 10am – noon Pacific Time zone. So this is your final change to Sign Up Now: Database Release Strategy and Patching Best Practices on Feb 4 – 10am PST.
Photo by Etty Fidele on Unsplash
Why you want to participate?
Roy, Daniel and I will kick of this series with the Episode 1: Database Release Strategy and Patching Best Practices for a reason. We get a ton of question regarding both topics every day. Everybody wants to know about Support time frames and life cycle, about the following releases “after” 19c. And there are patching questions. We get standard opatch topics, datapatch questions. And not to forget, you ask us everything regarding OJVM.
Feb 4, 2021 (10am-12pm PT) – Release Strategy and Patching Best Practices
We will start the series with an overview and outlook about the best release strategy for the next years. But when we talk about Release Strategy and Upgrades, the Patching topic is nearby as well. You’ll get deep insights and recommendations for database patch, OJVM, installation and patching in one pass. And of course tips and tricks about datapatch as well.
This is why we put this web seminar together. 1 hrs 45 minutes with a break in between. And then you’ll know everything about these topics. There won’t be any doubt anymore – and if you want to ask us about something we haven’t covered, we are there for 2 hours to answer all your question in the QA.
Of course, our webinars are free of marketing slides. We want to talk about reality, about facts and figures, about things which are important for you. This is our goal. This is why you want to participate. It is your time – and we don’t want to waste your time.
How do you register?
This is the page one click – and then you’ll tune in tomorrow.
Will it be recorded?
Yes, it will be. We will publish the on-demand video as soon as it has been staged after the seminar. And of course, the slides will be available right before the broadcast starts as well.
You want more?
We didn’t bore you? And you plan to upgrade or migrate soon? Then you may want to sign up to the following web seminars as well. We scheduled Episode 2-6 already in a (mostly) bi-weekly interval. Find the description and the registration information here:
We are looking forward to talk to you tomorrow!
–Mike
Can i still register for today webinar?
Hi Leonardo,
I hope it worked – and you can register even minutes before. I hope you’ve tried.
Cheers,
Mike
I attended the webinar, which I recommend greatly. But I had to drop off for a work meeting around the time you discussed the recommended “Out-of-Place Patching”. For Patch 32126883 [Combo of OJVM Component Release Update 12.2.0.1.210119 + Grid Infrastructure Jan 2021 Release Update 12.2.0.1.210119], “Out-of-Place Patching” is simple enough for the database, but what about the GI? Is it as easy as: 1) Cloning the GI binaries, 2) crsctl stop crs; 3) crsctl start crs using new GI_HOME? Is there a document describing each step? We have a Standalone/Restart Primary and Standalone/Restart Standby.
Another question is in regards to how to identify if OJVM is used. We have OJVM installed, but our customer does not know if they use OJVM or not. In 2217053.1 [RAC Rolling Install Process for the “Oracle JavaVM Component Database PSU/RU” (OJVM PSU/RU) Patches] under “Is OJVM used?”, contains SQL that queries v$session. Is there a better SQL query to look at OJVM history?
Hi Bill,
regarding OJVM and the check:
There is no better or more reliable way to check whether OJVM is used or not as mentioned in the MOS note.
For GI OOP patching, please see:
My Oracle Support Banner
Grid Infrastructure Out of Place ( OOP ) Patching using opatchauto (Doc ID 2419319.1)
In addition, use your preferred search engine and check for “out of place patching grid infrastructure 19c”.
I found right away several very well written blog posts by:
Rene: https://blog.pythian.com/silent-out-of-place-patching-oracle-19c-gi/
Michael: https://mdinh.wordpress.com/2020/08/19/minimal-downtime-grid-infrastructure-out-of-place-patching/
and others.
And something in the doc, too:
https://docs.oracle.com/en/database/oracle/oracle-database/19/cwlin/zero-downtime-oracle-grid-infrastructure-patching.html#GUID-471B87BF-3457-47BD-8858-316F4921EEE6
Cheers,
Mike
Mike,
In all the blogs about patching, I see that everyone is skipping the system space check which is very well documented in the patch documentation.
opatch prereq CheckSystemSpace
Is there a reason not do a system space check prior to patching?
Thanks,
Arun
Hi Arun,
you are so right – and I forget it all the time.
I hope, I won’t forget in April 🙂
Cheers,
Mike