My Belgium friend Phillipe Fierens raised a great question on Twitter last week and dropped me an email again after having a discussion with his client:
For Phillipe and myself the answer is pretty clear and straight forward:
There is no minor upgrade anymore since every (patch set) release is a full release and since new parameters, parameter values, features and whatever appears even in patch sets.
But the following discussion on Twitter with comments from all sides made me think about why people would honestly declare going for instance from 188.8.131.52 to 184.108.40.206 as a minor upgrade whereas going to 220.127.116.11 is seen as a major upgrade?
Let me summarize why I completely disagree – and actually Dom Giles nailed it:
- Since Oracle Database 18.104.22.168 we deliver patch sets as a full release
- A patch set can contain not only new parameters or parameter values but may occasionally also contain new features (typical examples in Oracle 22.214.171.124 are the new value for optimizer_dynamic_sampling=11 or the DBMS_REDACT package)
- Therefore you will have to do exactly the same amount of testing, regardless of going to Oracle Database 126.96.36.199 vs Oracle Database 188.8.131.52 – it is ZERO difference in the tests, the time, the effort, the manpower …
You don’t believe me? Then please check MOS Note:1962125.1 (Oracle Database – Overview of Database Patch Delivery Methods). Scroll down a bit to Testing Recommendations By Patch Type and see the rightmost column of this table headlined “Patch Set Release”:
I hope this clarifies it all.
There is no “minor” patch set upgrade anymore. Even though I would love to tell you that going from 184.108.40.206 to 220.127.116.11 is just a minor hop it will require exactly the same testing and evaluation work then going to Oracle Database 18.104.22.168.
But going to Oracle Database 22.214.171.124 will mean that you are under Premier Support until end of June 2018 – whereas Free Extended Support for Oracle Database 126.96.36.199 will end in May 2017.
The first two digits identify the major database release number. So, going from 9 to 10 to 11 to 12 is a major upgrade. Going from 188.8.131.52 to 184.108.40.206 is a component specific release number upgrade, so many will refer to it as minor upgrade.
I blogged about something very similar about a year and a half ago. http://www.peasland.net/2014/12/29/whats-a-major-version-anyway/
There are no "minor" upgrades any more.
Disagree – the doc does explain the release number and this part is carried over I believe since the 8i days.
But it has nothing to do with the database upgrade. And again – I repeat myself – there is no such thing as a FIRST release anymore. Every release is a FULL release. You will see a ton of changes in the next release of the database as you saw with 220.127.116.11 as you saw with 18.104.22.168 and potentially as you’ll see with the first patch set for the next release of the database.
Thanks Brian 🙂
Disagree. Compared to changes between 9i to 10g to 11g to 12c, changes between 22.214.171.124 to 126.96.36.199 are minor. The method of delivery is just to make it easy to rollback in case of failed upgrade. It has nothing to do with the fact that it is a major or minor upgrade. Major upgrade implies major feature changes, not how the upgrade is delivered. The new features guide is a good measure of whether or not an upgrade is major or minor.
sorry to insist but I speak explicitly about upgrade since we deliver all patch sets as a full release – i.e. 188.8.131.52. Things may be different when you look back to Oracle 9i and Oracle 10g.
Look at the features being introduced in 184.108.40.206 over 220.127.116.11 – DBIM is just a huge example but there are tons of others in almost all areas, from optimizer, to SPM, to parallel to … etc etc.
And unfortunately not all changes make it into the new features guide, especially when we talk about changes with the optimizer or parallel or SPM …