Planning an Upgrade to 14c (14.1.2.0.0)

Before you begin an upgrade, understand the limitations of the upgrade and how the upgrade impacts your production environment.

See here for details.

Upgrading and Preparing Your Oracle Databases for 14c

It is important to understand the database requirements for upgrade. If required, prior to the upgrade you may need to upgrade your database to a supported version.

See here for details on some of the tasks associated with preparing your Oracle database for an upgrade to 14c (14.1.2.0.0).

Understand how your pre-upgrade environment will be affected by the upgrade.

When upgrading your existing SOA Suite 12c environment to SOA Suite 14c (14.1.2.0.0), you should understand how your pre-upgrade environment will be affected by the upgrade. For example, schemas and domain directory upgrades are performed "in place" which updates the existing files during the upgrade. The 14c (14.1.2.0.0) Oracle home binaries are upgraded using the new 14c container image.

The upgrade to 14c (14.1.2.0.0) includes the midtier and the schemas. You cannot perform a midtier-only or schema-only upgrade.

The following list describes how the upgrade is performed for the following Infrastructure and SOA Suite components:

• Oracle WebLogic Server, JRF and SOA Oracle Home Binaries

  You will be using new 14c SOA Suite container image which has Oracle Infrastructure ( WebLogic Server and JRF) 14c (14.1.2.0.0) and the Oracle SOA Suite and Serivce Bus 14c (14.1.2.0.0) distribution binaries.

• Schemas - Upgraded In Place

  The schemas are upgraded "in place" which means that the Upgrade Assistant updates and overwrites the existing 12c schemas during the upgrade process. The servers must be down during this process.

• Instances - Migrated during the schema upgrade

  The upgrade of active and closed instances happens automatically as part of the schema upgrade. You can manage the upgrade using administration scripts.

• Domain Directory Reconfiguration - Upgraded In Place

  The existing SOA domain is upgraded "in place". During the upgrade you will provide the location of the existing 12c SOA domain and this domain will be reconfigured to new SOA 14c (14.1.2.0.0) home directory.

Understanding the Starting Points for a SOA Suite 14c (14.1.2.0.0) Upgrade

Verify that the pre-upgrade environment is at a supported version before an upgrade.

You can upgrade to Oracle SOA Suite and Service Bus 14c (14.1.2.0.0) from the following production starting point:

• SOA Suite and Service Bus 12c (12.2.1.4.0)

SOA Domain Compatibility and Upgrade Restrictions

Read and understand how all of the components within your pre-upgrade domain interact with the upgraded 14c (14.1.2.0.0) components. See Understanding the Interoperability and Compatibility Restrictions Before You Upgrade for details.

Review the domain upgrade restrictions before starting the upgrade. See Understanding SOA Domain Upgrade Restrictions for details.

Oracle SOA Domain Pre-Upgrade Tasks

Before you start the upgrade process be sure to complete the required pre-upgrade tasks for your components and environment. See Oracle Fusion Middleware Pre-Upgrade Tasks for details.

In addition to the Oracle Fusion Middleware pre-upgrade requirements, you may also be required to complete additional SOA-specific upgrade tasks depending on your pre-upgrade environment.

Review the SOA-specific and Servic Bus specific pre-upgrade tasks that apply to your environment.

Upgrading Oracle SOA Suite and Oracle Service Bus

This section provides the end-to-end procedure for upgrading a 12.2.1.4 Oracle SOA Suite and Oracle Service bus production environment in Kubernetes to 14c (14.1.2.0.0).

Oracle strongly recommends to create a complete backup (backup of database and domain home in persistence volume) of your existing domain before you begin the upgrade.

Refer Upgrading SOA Suite and Upgrading Oracle Service Bus for details.

Using GUI Mode

To perform Oracle SOA Suite domain upgrade in a container environment using GUI mode, we need display terminal.Perform below steps to start a VNC session using the Oracle SOA Suite 14.1.2.0.0 container image and the existing 12.2.1.4.0 domain home in persistent volume. Then using this VNC session you can perform upgrade using GUI mode.

Using silent mode

Alternatively, to perform Oracle SOA Suite domain upgrade in a container environment in silent mode, you can run the helper upgrade script domain-upgrade.sh available at ${WORKDIR}/create-soa-domain/domain-upgrade to perform Oracle SOA Suite domain upgrade from 12.2.1.4.0 to 14.1.2.0.0.

Refer Oracle SOA Suite Domain Release Upgrade.