In early February, Oracle published some important data on its Support site. If you have access to My Oracle Support, details can be viewed under Document Id 742060.1 (“Release Schedule of Current Database Releases”). In this letter we would like to point out the most important points.
First of all, there is good news for everyone who still uses Oracle Database release 188.8.131.52. The extended support of this will be extended by no less than one and a half years until December 2018 at no additional cost. In addition, extended support for release 184.108.40.206 will continue at no additional cost until July 2019. This is probably related to the timing of the new release 12.2, which has taken some time.
The drawing below shows the current support periods:
This extension should not be seen as an encouragement to continue running on 220.127.116.11 longer than necessary. It is, however, an acknowledgment of the reality that preparing for an upgrade of business-critical environments to version 12 simply takes time and that this certainly also applies to application suppliers. Extending the support gives a good amount of extra “air” to these stretches so that they can be performed without undue “rush”.
The extension for 18.104.22.168 is also welcome. A large number of our customers have already implemented this version and it is nice to know that this database version will still be well supported in the coming years. Please note: this concerns 22.214.171.124 and NOT 126.96.36.199. For example, if you use Oracle Standard Edition One (version 188.8.131.52), this extension does not apply and an upgrade to Standard Edition Two (version 184.108.40.206) is still necessary for support.
The second big news is Oracle’s confirmation of the imminent availability of Oracle Database version 12.2 for local use. As a cloud service, this database has been available for some time, but the vast majority of users prefer to install and use it in their own IT environment. Oracle has now made version 12.2 available for the Oracle Exadata system and the introduction for regular Linux servers will follow in mid-March. The variants for the Oracle Database Appliance and Microsoft Windows should then follow before the summer.
For customers who are still using version 11.2, we recommend that they focus on an upgrade to version 12.2 in their migration plans, unless the migration must have taken place within a few months. Thanks to the fact that version 12.2 has been in use for some time in cloud environments, it is likely that any teething problems have already been largely recognized and solved by the time of the upcoming release.
If you have further questions about this matter or if you would like advice about an upgrade, please do not hesitate to contact us.
DBA.nl is the all-round database expert specialized in setting up, maintaining and monitoring database environments. In addition, we provide advice and remove performance problems.
In almost every organization the most important and most structured data is located in a few critical tables within your...
CVE-2015-0235 aka “The GHOST Vulnerability” On January 27, a vulnerability was discovered in the Linux glibc library...
"Oracle counts all servers when using VMware vSphere from version 5.1" Several sources on the internet report that Oracl...