Why Oracle database skipped 5 version and jumped to 18c?
Oracle 18c database is new flagship database from Oracle announced in Oracle Open World 2017.
The previous database version released was 12c or 12.2.0.1. Oracle is simplifying the release cycle and aligning with the industry standard by use of the year with a version number. So instead of becoming 12.2.0.2 it becomes 18c.
These steps enable the DBA and developer to have access to the new features and functionalities sooner than later and test these features faster. As you can see from the history of Oracle Database releases. Earlier versions as more frequent releases but as database become more mature and packed with automation, the releases cycle started to have approx a 5yrs gap. This certainly means that there is a lot of R&D going the background and when Oracle releases the product with over 500 new features, DBA and Developers were not able to cope up with all the functionalities and implement in their productions systems.
1979 Version 2
1983 Version 3
1984 Version 4
1985 Version 5
1988 Version 6
1997 Version 7
1997 Version 8
1999 Version 8i
2002 Version 9i
2003 Version 10g
2007 Version 11g
2013 Version 12c
2017 Version 18c
Oracle’s change to annual releases addresses both the delay in getting new features out, as well as the number of changes introduced. This should enable the DBAs and Developers to rapidly test new features and functionalities.
The new release method has 3 tier releases. First-tier as Major Release, Second tier as Release Update (RU) and third tier as Release Update Revision (RUR)
The RU replaces the older Bundled Patch (BP), and should be released on a quarterly basis. The RU includes function fixes, security fixes, functional enhancements and emergency patches. Most development environments should patch at the RU level.
The third tier is the Release Update Revision (RUR) which is intended to extend the functional life of an RU. The RUR focuses on security and regression patches only. RURs have a limited life, and would normally be expected to be used to support Production patching until the production environment can be patched to the latest RU for the major Release version.
Smaller the number of changes between releases should mean that upgrades between releases would be simpler and fast.
Oracle Database Release Schedule on MOS note
Technology Expert. Sky is the limit.. ??????????
6 年People may disagree, but as per my understanding: there is a key role played by numerologists in the naming of the new version.
Senior Solution Engineering Manager, MEA
6 年Great read Arush, much better than my theory when they first took it out. :)
Business Development Manager @ Sogeti | Sales Professional
6 年Great explanation of the changes to Oracle Database release cycle. A good read for DBAs. Thanks Arush.