By Mike Dietrich-Oracle on Apr 29, 2016
It's so funny - for years I discuss with customers minimal downtime upgrade strategies back and forth, up and down. I saw DBAs really hunting to save a few seconds potential downtime - and I always take this serious as there is usually a real reason behind that. Just to learn a few days later by repeating experience that my work Windows7 laptop goes down to apply upgrades ... and this takes looooooooong .... sometimes it takes a lengthy +30 minutes of quiet time. Whereas my OL6 VBox image applies upgrades in the background and needs a simple restart to be back in less than a minute or so.
Different strategies of course.
For those who think I'm writing nonsense about the upgrade of my Win7 on my Lenovo x230 with 16GB of RAM, an i5-320M cpu and a 5400rpm WD spinning disk here's a screenshot taken from one of those upgrades where I sat already 15 minutes waiting ... waiting ... waiting ...
As Win7 had to configure the upgrades afterwards, once it was done with restarting I had to wait another 10 minutes for completion. And no, my laptop is not broken (not that I know) - it's 3 years old and heavily used of course. But all running fine usually ...
Of course I discussed with a ton of people why you should upgrade now to Oracle Database 18.104.22.168 now! - and stay away from that "we go live on the 2nd release only" thinking as there's no such thing as THE 2nd release anymore.
But whatever my position on upgrades is, I can ensure that we don't discuss methods like this internally to force you to upgrade ...
... not yet *haha* !!!
PS: The picture is not a fake - you can watch the 41 seconds youtube video here