There are currently several different releases of Oracle Database available from long term releases to innovation releases (temporary releases which contain new enhancements and features which will be present in the next long term release). As time goes by, many releases fall out of not only premier support but also extended support. When releases come out of premier support, patches and bug fixes only become available when you purchase extended support. However, when extended support ends for a release, new updates, patches, and bug fixes generally are no longer available. In addition, extended support is only available for long term releases. With releases coming into and out of support, you may be pressured to upgrade your database to a newer release. However, there are some important things to know before upgrading your Oracle Database.

Recent Oracle Database Releases and Support Dates

Oracle Database ReleaseType of ReleasePremier Support End DateExtended Support End Date
11.2.0.4.xLong Term Release1/1/201512/31/2020
12.1.0.2.xLong Term Release7/31/20187/31/2022
12.2.0.1.xInnovation Release11/30/2020*Not available
18.0.0.0.xInnovation Release6/30/2021Not available
19.0.0.0.xLong Term Release4/30/20244/30/2027

*=Limited Error Correction and limited patching are available until March 31, 2022.

NOTE: If you are on a database version older than or including 11.2.0.4.x, you need to seriously consider upgrading your database as soon as possible as all database releases older than 12c are no longer covered under any support.

Before You Upgrade

Operating Systems

When you see your current Oracle Database release is close to the end date for premier support or especially extended support, you may feel pressured to upgrade your database to a new release such as 19c (19.0.0.0.x). While it is important to be on the latest release with the latest features, security patches, bug fixes, and support, you also need to consider the other Oracle products installed in your databases along with the operating systems hosting your databases. There are many different ways to upgrade an Oracle Database. In-place upgrades and database migrations are common ways to upgrade a database from one version to another. In-place upgrades are an easy way to upgrade your database because you can use the Database Upgrade Assistant (DBUA), a graphical interface allowing you to easily upgrade your database in the same host. However, an in-place upgrade will only work if the operating system supports the source database version and the destination database version. If you are upgrading from one database release to another which is not supported on the operating system you have, you will either need to upgrade your operating system or consider migrating your database to a new server using services such as Data Pump, Transportable Tablespaces, or Oracle Data Guard. The following table lists all supported operating system versions for each Oracle Database release:

Oracle Database Release11.2.0.4.x12.1.0.2.x12.2.0.1.x18.0.0.0.x19.0.0.0.x
IBM AIX on POWER Systems5.3, 6.1, 7.1, 7.26.1, 7.1, 7.26.1, 7.1, 7.26.1, 7.1, 7.27.1, 7.2
LinuxRHEL/Oracle Linux 4, 5, 6, 7, SLES 10, 11, 12RHEL/Oracle Linux 5, 6, 7, 8, SLES 11, 12RHEL/Oracle Linux 6, 7, SLES 12, 15RHEL/Oracle Linux 6, 7, SLES 12RHEL/Oracle Linux 7, 8, SLES 12, 15
Solaris10, 1110, 1110, 1110, 1111
WindowsXP, Vista, 7, 8, 8.1, 2003, 2003 R2, 2088, 2008 R2, 2012, 2012 R27, 8, 8.1, 10, 2008, 2008 R2, 2012, 2012 R27, 8, 8.1, 10, 2012, 2012 R2, 20167, 8.1, 10, 2012, 2012 R2, 20168.1, 10, 2012 R2, 2016, 2019

NOTE: Bolded database versions in the above table are versions which are supported across all database releases above. For example, Red Hat Enterprise Linux 7 and Oracle Linux 7 are supported with Oracle Database 11.2.0.4.x and 19.0.0.0.x. This means that there will be no certification issues if you plan an in-place upgrade of your Oracle Database from 11.1.2.4.x to 19.0.0.0.x if it is hosted in RHEL 7 or Oracle Linux 7.

Using the above table, if you are on an operating system release in bold, you should have no problems with regards to operating system support when performing an in-place upgrade. If you are on a release which the release you are upgrading to does not support your current operating system, you will need to take an extra step to determine if you would like to upgrading your operating system first (if performing an in-place upgrade) or if you would prefer to do a database migration instead. It is possible to perform an in-place upgrade from all versions listed above to 19c including 11.1.2.4.0.

Oracle Products

In addition to operating system support, it is important to make sure that your current releases of various Oracle products such as Forms, ADF, APEX, and Oracle Access Management will remain certified with the new release. We will take each Oracle product below and list the Oracle Database versions certified with each release and assess the upgrade paths you may consider taking. It is highly advised that you upgrade your Oracle Database to the 19c release. In our examples below, we will highlight some guidelines when considering an upgrade to Oracle Database 19c.

Oracle WebLogic Server

Oracle WebLogic Releases
11.2.0.4.x12.1.0.2.x12.2.0.1.x18.0.0.0.x19.0.0.0.x
10.3.5.0.0YesNoNoNoNo
10.3.6.0.0YesYesYesYesYes
12.1.1.0.0NoYesNoNoNo
12.1.2.0.0YesYesNoNoNo
12.1.3.0.0YesYesYesNoNo
12.2.1.0.0YesYesYesNoNo
12.2.1.1.0YesYesYesNoNo
12.2.1.2.0YesYesYesYesYes
12.2.1.3.0YesYesYesYesYes
12.2.1.4.0YesYesYesYesYes
14.1.1.0.0YesYesYesYesYes
  • If you are using Oracle WebLogic Server 10.3.4 or earlier, you need to upgrade to either 10.3.6, the latest 12c release, or the new release, 14.1.1. In case your WebLogic installation is running another Oracle Fusion Middleware product such as Oracle Forms, APEX, or ADF, please make sure that your version of that product is certified with the release of Oracle WebLogic Server you are planning to upgrade to.
  • If you are on an older version of Oracle WebLogic Server 12c and you are planning to upgrade to Oracle Database 19c, you will need to at least migrate to the latest release of Oracle WebLogic Server 12c, 12.2.1.4.0. WebLogic upgrades from older 12c releases to newer releases usually require an installation of a new Oracle home followed by either re-provisioning your WebLogic domain or configuring a new domain.

Oracle Forms and Reports

Oracle Forms & Reports Releases
11.2.0.4.x12.1.0.2.x12.2.0.1.x18.0.0.0.x19.0.0.0.x
11.1.1.4.0YesNoNoNoNo
11.1.1.6.0YesNoNoNoNo
11.1.1.7.0YesYesNoNoNo
11.1.2.0.0YesNoNoNoNo
11.1.2.1.0YesYesNoNoNo
11.1.2.2.0YesYesYesNoNo
12.2.1.0.0YesYesYesNoNo
12.2.1.1.0YesYesYesNoNo
12.2.1.2.0YesYesYesYesYes
12.2.1.3.0YesYesYesYesYes
12.2.1.4.0YesYesYesYesYes
  • If you are using Oracle Forms and Reports 10g or older (4.5, 6i, 9i, etc.), you will need to upgrade to Oracle Forms 12c to be able to use Oracle Database 19c. If you are using Oracle Forms releases older than 6i, you will first need to upgrade to either 6i or 10g prior to upgrading to 12c. PITSS’ tool, PITSS.CON, can help you upgrade to the latest and greatest release of Oracle Forms and Reports.
  • If you are using Oracle Forms and Reports 11g or 11gR2, you will need to upgrade to Oracle Forms 12c to be able to use Oracle Database 19c. Usually a recompile of your Forms and Reports application is all that is required to upgrade your application to 12c (with the exception of installing a new 12c WebLogic environment). Depending on the complexity of your Forms application, there are some cases where some re-engineering may be required especially if you use DADs or mod_plsql. PITSS’ tool, PITSS.CON, can help you analyze all which is required for upgrading from 11g to 12c.
  • If you are on older releases of Oracle Forms and Reports 12c such as 12.2.1.0.0 or 12.2.1.1.0, you will need to upgrade to the latest release of Oracle Forms 12c to be able to use Oracle Database 19c. A recompile of your Oracle Forms and Reports application is all that is required, but you will need to install a new Oracle home for Oracle Forms and Reports 12.2.1.4.0 and then either re-provision your existing WebLogic domain for the new Oracle home or configure a new domain.
  • For Forms 12c, the version number will match what WebLogic uses.

Oracle Application Express (APEX)

Oracle APEX Releases
11.2.0.4.x12.1.0.2.x12.2.0.1.x18.0.0.0.x19.0.0.0.x
4.2.1YesNoNoNoNo
4.2.2YesNoNoNoNo
4.2.3YesNoNoNoNo
4.2.4YesNoNoNoNo
4.2.5YesYesNoNoNo
4.2.6YesYesNoNoNo
5.0YesYesYesNoNo
5.0.4YesYesYesNoNo
5.1YesYesYesNoNo
5.1.1YesYesYesYesNo
5.1.2YesYesYesYesNo
5.1.3YesYesYesYesNo
5.1.4YesYesYesYesNo
18.1YesYesYesYesNo
18.2YesYesYesYesNo
19.1YesYesYesYesYes
19.2YesYesYesYesYes
20.1YesYesYesYesYes
  • If you are using an APEX version older than 19.1, you will need to first upgrade APEX in your database to either version 19 or 20 prior to upgrading your database to 19c.
  • You will also need to consider the version of Oracle REST Data Services (ORDS) before upgrading your database to 19c. ORDS serves as a bridge between APEX and your application server such as WebLogic or Apache Tomcat. More information on ORDS is shown in the next section.

Oracle REST Data Services (ORDS)

Oracle REST Data Service Releases
11.2.0.4.x12.1.0.2.x12.2.0.1.x18.0.0.0.x19.0.0.0.x
3.0.6YesYesYesNoNo
3.0.7YesYesYesNoNo
3.0.8YesYesYesNoNo
3.0.9YesYesYesNoNo
3.0.10YesYesYesNoNo
3.0.11YesYesYesNoNo
3.0.12YesYesYesNoNo
18.1YesYesYesNoNo
18.1.1YesYesYesNoNo
18.2YesYesYesNoNo
18.3YesYesYesNoNo
18.4YesYesYesNoNo
19.1YesYesYesNoNo
19.2YesYesYesNoNo
19.4YesYesYesYesYes
20.2YesYesYesYesYes
  • If you are using an ORDS version older than 19.4, you will need to re-deploy ORDS into your application server using either version 19.4 or 20.2.
  • You will also need to consider the version of Oracle Application Express (APEX) before upgrading your database to 19c.

Oracle Application Development Framework (ADF)

Oracle ADF Releases
11.2.0.4.x12.1.0.2.x12.2.0.1.x18.0.0.0.x19.0.0.0.x
11.1.1.4.0YesNoNoNoNo
11.1.1.5.0YesNoNoNoNo
11.1.1.6.0YesNoNoNoNo
11.1.1.7.0YesYesNoNoNo
11.1.1.9.0YesYesYesYesYes
12.1.3.0.0YesYesYesNoNo
12.2.1.0.0YesYesYesNoNo
12.2.1.1.0YesYesYesNoNo
12.2.1.2.0YesYesYesYesYes
12.2.1.3.0YesYesYesYesYes
12.2.1.4.0YesYesYesYesYes
  • If you are using ADF 11.1.1.7.0 or older 11g releases, you have the option to upgrade to ADF 11.1.1.9.0 to use Oracle Database 19c. This can be done using in-place upgrades of both Oracle WebLogic Server and ADF. You also have the option to upgrade to ADF 12c by installing a new Oracle WebLogic Server 12c environment.
  • If you are using ADF 12.1.3.0.0, 12.2.1.0.0, and 12.2.1.1.0, you will need to upgrade ADF to the latest release of 12c to use Oracle Database 19c. You will need to install a new Oracle home for ADF 12.2.1.4.0 and then either re-provision your existing WebLogic domain for the new Oracle home or configure a new domain.
  • You will also need to consider the version of Oracle WebLogic Server before upgrading your database to 19c. For ADF 12c, the version number will match what WebLogic uses.
  • Developers will also need to upgrade their JDeveloper to the same release as ADF and then upgrade the code from within JDeveloper.

Oracle BI Publisher

Oracle BI Publisher Releases
11.2.0.4.x12.1.0.2.x12.2.0.1.x18.0.0.0.x19.0.0.0.x
11.1.1.6.0YesNoNoNoNo
11.1.1.7.0YesYesNoNoNo
11.1.1.9.0YesYesYesYesYes
12.2.1.0.0YesYesYesNoNo
12.2.1.1.0YesYesYesNoNo
12.2.1.2.0YesYesYesYesYes
12.2.1.3.0YesYesYesYesYes
12.2.1.4.0YesYesYesYesYes
  • If you are using BI Publisher 11.1.1.7.0 or older 11g releases, you have the option to upgrade to BI Publisher 11.1.1.9.0 to use Oracle Database 19c. This can be done using in-place upgrades of both Oracle WebLogic Server, Oracle Business Intelligence Enterprise Edition, and BI Publisher. You also have the option to upgrade to BI Publisher 12c by installing a new Oracle WebLogic Server 12c environment with Oracle BI Enterprise Edition 12c.
  • If you are using BI Publisher 12.2.1.0.0 and 12.2.1.1.0, you will need to upgrade BI Pulisher to the latest release of 12c to use Oracle Database 19c. You will need to install a new Oracle home for BI Enterprise Edition 12.2.1.4.0 and then either re-provision your existing WebLogic domain for the new Oracle home or configure a new domain.
  • You will also need to consider the version of Oracle WebLogic Server and Oracle BI Enterprise Edition before upgrading your database to 19c. For BI Publisher 12c, the version number will match what WebLogic uses.

Oracle Access Management (OAM)

Oracle Access Management Releases
11.2.0.4.x12.1.0.2.x12.2.0.1.x18.0.0.0.x19.0.0.0.x
11.1.2.3.0YesYesYesYesYes
12.2.1.3.0YesYesYesYesYes
12.2.1.4.0YesYesYesYesYes
  • For Oracle Access Manager, no considerations need to be made for performing an in-place upgrade of your Oracle Database. All OAM releases 11.1.2.3.0 or greater will work with Oracle Database 11gR2, 12c, 18c, and 19c. However, it is highly recommended that you back up your database prior to performing any database upgrade.

Oracle Internet Directory (OID)

Oracle Internet Directory Releases
11.2.0.4.x12.1.0.2.x12.2.0.1.x18.0.0.0.x19.0.0.0.x
11.1.1.4.0YesNoNoNoNo
11.1.1.5.0YesNoNoNoNo
11.1.1.6.0YesNoNoNoNo
11.1.1.7.0YesYesNoNoNo
11.1.1.9.0YesYesYesYesYes
12.2.1.3.0YesYesYesYesYes
12.2.1.4.0YesYesYesYesYes
  • If you are using OID 11.1.1.7.0 or older 11g releases, you have the option to upgrade to OID 11.1.1.9.0 to use Oracle Database 19c. This can be done using in-place upgrades of both Oracle WebLogic Server and OID. You also have the option to upgrade to OID 12c by installing a new Oracle WebLogic Server 12c environment.
  • If you are doing a new installation of OID (e.g. when upgrading from 10g or 11g to 12c), you will need to migrate all your LDAP resources as well as any Resource Access Descriptors (RADs) to the new OID environment.
  • You will also need to consider the version of Oracle WebLogic Server before upgrading your database to 19c. For ADF 12c, the version number will match what WebLogic uses.

PITSS.CON and Oracle Database Upgrades

The latest release of PITSS.CON is also compatible with Oracle Database 19.0.0.0.x. If you are planning to upgrade your database to 19c and the database also hosts your PITSS.CON repository, there are a few considerations you will need to make:

  • Make sure your PITSS.CON installation is at the latest release. Please contact PITSS to see if you are at the latest release as well as to help you upgrade to the latest PITSS.CON release if you are not at the latest release.
  • If you are doing an in-place upgrade of the PITSS.CON database, it is advised that you take an export of the MIG and PITSS.CON user schemas using Data Pump for backup purposes in case any problem occurs. Most likely the upgrade will not cause any problems with the existing installation, but having a backup will help.
  • If you are doing a database migration of the PITSS.CON, do NOT use Data Pump to export the PITSS.CON schemas (including MIG) to the new database. Please contact PITSS for assistance with moving PITSS.CON from one database to another. Otherwise, problems will occur with your PITSS.CON license.

Please contact PITSS today if you would like assistance with helping you upgrade your Oracle environments to be compatible with Oracle Database 19.0.0.0.x.

Sources: Oracle Support Document ID 742060.1