Oh, how often have I heard this phrase:
“We’ll wait for the second release!”
And sometimes it makes me really anxious and angry at the same time when I hear that.
Anxious because it means that somebody has no strategy for the database upgrades/migrations and is just postponing necessary tasks to sometime in the future. Easy deal but not very clever.
Angry because this is a way of thinking from the 90s/00s when Oracle had this “10.1”, then later “10.2” strategy in database releases. But we are in 2014 now. And things have changed. Changed a lot in fact.
I’m probably not the only person who would love to see if we’d remove this “first” and “second” release tags. This has become obsolete with Oracle 11.1. We were telling customers officially that this is the brand new fantastic Oracle Database 11g release. But in fact it was – from the coding perspective – more or less a very stable 10g. In my workshops I did call it Oracle 10.3 with a marketing sticker on it. And as far as I can see the customer’s I’ve had helped with going live on Oracle Database 188.8.131.52 were quite happy. Some really large shops still work with this release today with hundreds of databases in production.
But honestly most of the changes got introduced with Oracle Database 11.2. And not for a small number of customers this meant waiting for the first patch set (which since then has become a full release). Plenty of people went live with Oracle Database 184.108.40.206. But a lot of the remarkable changes got introduced not in Oracle 11.1 but in Oracle 11.2. Just remember things such as the move from Clusterware to Grid Infrastructure. But also minor things such as DEFERRED_SEGMENT_CREATION and plenty of optimizer news.
Now with Oracle Database 12c and the first patch set (full release) 220.127.116.11 I have heard this again – and I see it on the mailing list as well once a week:
“When will Oracle 12.2 be available?”
Well, that’s the misconception. It’s true, Oracle Database 18.104.22.168 has new features and extensions. But it has also many fixes over the already very stable Oracle 22.214.171.124. Why should anybody wait for Oracle 12.2 now? Because it’s supposed to be THE SECOND release? Forget this – this is thinking from the old days.
We are in year 2014 now.
And then spend a minute to look closer to the Support Policy.
- Oracle Database 11.2 will go out of Premier Support in 6 months. Yes!!! 6 months
- And correct, we’ll give everybody on Oracle 126.96.36.199 more than one full year of Extended Support for free
- For Oracle 188.8.131.52 Extended Support will end 27-AUG-2015
That means if you plan to stay on Oracle 184.108.40.206/4 for a longer period you’ll either have to calculate 20% extra of your support fee for the 2nd year of Extended Support. Or you prefer to “hope“.
I can’t tell you when Oracle 12.2 will be available – and I don’t care. Usually people wait for the first patch set anyways which gets releases based on experience from the past 3 databases releases roughly a year and a bit after the initial release. Just do the math and you’ll see where you end up with this strategy.
My recommendations are:
- Stop thinking about THE SECOND release
- Evaluate Oracle Database 220.127.116.11 now – not tomorrow
- Look at the Support Policy – you need to start your upgrades as soon as possible
PLEASE READ ON: