C Performing a Reduced Downtime Upgrade

If you are upgrading from Fusion Middleware 12c (12.2.1.3) release, then you can use this process to upgrade your multi-node domain without shutting down all of the servers at the same time.

Note:

Oracle Fusion Middleware 12c (12.2.1.3) is the only supported starting point for a reduced downtime upgrade. You cannot perform a reduced downtime upgrade if you are upgrading from a supported Fusion Middleware 11g or 12c (12.2.1.2.0 or earlier) release, or you do not have a multi-node environment. To perform a reduced downtime upgrade from 12c (12.1.3 or 12.2.1.2), you must first upgrade to 12.2.1.3 using the standard upgrade process.

The procedures described in this section are based on the Oracle Fusion Middleware Standard Installation Topology (SIT) and require that you have a multi-node environment. The standard installation topology for Oracle Fusion Middleware Infrastructure has a standard WebLogic Server domain that contains an Administration Server and a cluster containing two Managed Servers. Host 1 is used to describe the procedures performed on the host with the Administration server and Host 2 is used to describe the procedures performed on the other managed server host(s). If you have more than 2 hosts in your environment, be sure to complete the procedures on each additional node.

Required Tasks that Must be Completed Before You Begin

Review the following before you begin a reduced downtime upgrade:

  • Review the preupgrade checklists for the components in your deployment. The checklists are found in each of the component-specfic upgrade guides. Some products may require additional steps before performing the upgrade.
  • Create a complete backup of the Oracle home (on all of the nodes), the entire domain directory (on all of the nodes) and component schemas before performing upgrade. In addition, Oracle recommends that you create a backup of UI customizations and the applications directory, in addition to domain directory.
  • Make sure that you are using the appropriate JDK version for this release. For this release the correct version is jdk1.8.0_211
  • If you are upgrading a shared component directory, back up the contents of the shared directory before upgrade. The configuration upgrade makes changes to these directories.
  • Make sure that your backups include any modified scripts, such as setStartupEnv.sh, for example. The upgrade will overwrite any customized files and you will lose your changes.

Performing the Upgrade on Host 1

Perform the following tasks on the machine that hosts the Administration server and serves as the primary machine for your deployment.

Stopping Components, Servers and Processes on Host 1

You must shut down all of the system components, processes, servers (including the Administration Server and any managed servers), and the node manager (if running).

Note:

The procedures in this section describe how to stop components, servers, and processes using the WLST command line or a script. You can also use the Oracle Fusion Middleware Control and the Oracle WebLogic Server Administration Console.
An Oracle Fusion Middleware environment can consist of an Oracle WebLogic Server domain, an Administration Server, multiple managed servers, Java components, system components such as Identity Management components, and a database used as a repository for metadata.

The components may be dependent on each other, so they must be stopped in the following order:
  • System Components (if any)
  • Managed Server(s)
  • Administration Server
  • Node Manager
Stopping System Components

To stop system components, such as Oracle HTTP Server, use the stopComponent script:

Navigate to the DOMAIN_HOME\bin directory and execute the following script for each component:
./stopComponent.sh component_name 
Stopping the Managed Servers
To stop a WebLogic Server Managed Server, use the stopManagedWebLogic script:
  1. Enter the following command:
    (UNIX) DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url
    (Windows)DOMAIN_HOME\bin\stopManagedWebLogic.cmd managed_server_name admin_url
  2. When prompted, enter your user name and password.
    Stop SOA servers and processes in this order:
Stopping the Administration Server

When you stop the Administration Server, you also stop the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.

To stop the Administration Server:
  1. Enter the following command:
    (UNIX) DOMAIN_HOME/bin/stopWebLogic.sh
    (Windows) DOMAIN_HOME\bin\stopWebLogic.cmd
  2. When prompted, enter your user name, password, and the URL of the Administration Server.
Stopping the Node Manager

To stop Node Manager, close the command shell/prompt in which it is running.

Alternatively, after having set the nodemanager.properties attribute QuitEnabled to true (the default is false), you can use WLST to connect to Node Manager and shut it down.

Uninstalling the Software

When performing a rolling upgrade, an empty directory is required for installing the new binaries prior to upgrading.

Note:

You must deinstall the upperstack components first, then deinstall JRF. After deinstalling the JRF, back up any remaining files and then delete all files in the directory. The installation directory must be empty.

Follow the instructions in this section to remove the software from the existing ORACLE_HOME. You will reinstall the new software into this same directory.

To start the Oracle Universal Installer in deinstallation mode, execute the following command:

ORACLE_HOME/oui/bin/deinstall.sh

If you want to uninstall the product in a silent (command-line) mode, see Running the Oracle Universal Installer for Silent Uninstallation in Installing Software with the Oracle Universal Installer.

Installing Oracle Fusion Middleware Infrastructure

Installing Fusion Middleware Infrastructure creates an Oracle home directory and lays down supporting software to install other Fusion Middleware products.

Before starting your upgrade, uninstall the software from the existing Oracle home, then use the Oracle Universal Installer to install the 12c (12.2.1.4.0) product distributions into the same Oracle home on the target system. You must install the product distributions on each host during the upgrade.

The supported JDK version for 12c (12.2.1.4.0) is 1.8.0_211. Make sure that you upgrade to the latest JDK version before installing the 12c (12.2.1.4.0) software.

Note:

If you are upgrading from a previous 12c release, then you must install the12c (12.2.1.4.0) distributions into a new Oracle home. Do not attempt to reuse the existing Oracle home for this upgrade. Upgrading to 12c (12.2.1.4.0) is not a patch release.
To install Oracle Fusion Middleware Infrastructure distribution:
  1. Sign in to the target system.
  2. Download the Oracle Fusion Middleware Infrastructure (fmw_12.2.1.4.0_infrastructure.jar) from Oracle Technology Network or Oracle Software Delivery Cloud to your target system.
  3. Change to the directory where you downloaded the 12c (12.2.1.4.0) product distribution.
  4. Start the installation program for Oracle Fusion Middleware Infrastructure:
    • (UNIX) JDK_HOME/bin/java -jar fmw_12.2.1.4.0_infrastructure.jar
    • (Windows) JDK_HOME\bin\java -jar fmw_12.2.1.4.0_infrastructure.jar
  5. On UNIX operating systems, the Installation Inventory Setup screen appears if this is the first time you are installing an Oracle product on this host.
    Specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location, and click Next.

    Note:

    The Installation Inventory Setup screen does not appear on Windows operating systems.
  6. On the Welcome screen, review the information to make sure that you have met all the prerequisites. Click Next.
  7. On the Auto Updates screen, select an option:
    • Skip Auto Updates: If you do not want your system to check for software updates at this time.

    • Select patches from directory: To navigate to a local directory if you downloaded patch files.

    • Search My Oracle Support for Updates: To automatically download software updates if you have a My Oracle Support account. You must enter Oracle Support credentials then click Search. To configure a proxy server for the installer to access My Oracle Support, click Proxy Settings. Click Test Connection to test the connection.

    Click Next.
  8. On the Installation Location screen, specify the location for the Oracle home directory and click Next.
    For more information about Oracle Fusion Middleware directory structure, see Understanding Directories for Installation and Configuration in Oracle Fusion Middleware Planning an Installation of Oracle Fusion Middleware.
  9. On the Installation Type screen, select Fusion Middleware Infrastructure and click Next.
  10. The Prerequisite Checks screen analyzes the host computer to ensure that the specific operating system prerequisites have been met.
    To view the list of tasks that are verified, select View Successful Tasks. To view log details, select View Log. If any prerequisite check fails, then an error message appears at the bottom of the screen. Fix the error and click Rerun to try again. To ignore the error or the warning message and continue with the installation, click Skip (not recommended).
  11. On the Security Updates screen, enter your My Oracle Support account information so you can receive the latest product information and security updates via your My Oracle Support account.
    This screen appears the first time you install an Oracle product on a host.
    If you do not have an Oracle Support account and you are sure that you want to skip this step, clear the check box and verify your selection in the follow-up dialog box.
  12. On the Installation Summary screen, verify the installation options that you selected.
    If you want to save these options to a response file, click Save Response File and enter the response file location and name. The response file collects and stores all the information that you have entered, and enables you to perform a silent installation (from the command line) at a later time.

    Click Install to begin the installation.

  13. On the Installation Progress screen, when the progress bar displays 100%, click Finish to dismiss the installer, or click Next to see a summary.
  14. The Installation Complete screen displays the Installation Location and the Feature Sets that are installed. Review this information and click Finish to close the installer.

Restarting Node Manager, Administration Server, Managed Servers and Components on Host 1

After the upgrade, you must restart the components, servers, and processes in the correct order.

Note:

The procedures in this section describe how to start servers and processes using the WLST command line or a script. You can also use the Oracle Fusion Middleware Control and the Oracle WebLogic Server Administration Console. See Starting and Starting Administration and Managed Servers and Node Manager in Administering Oracle Fusion Middleware.

The components must be started in the following order:

  • Node Manager
  • Administration Server
  • Managed Server(s)
  • System Components

Note:

If you are unable to successfully start any of the following components on Host 1, do not proceed with the upgrade on the remaining Hosts. You must first resolve the issues with the components on Host 1.

Note:

Windows Users Only: When restarting the servers on a Windows operating system, the upgraded domain might fail with a parsing exception. To fix this parsing error, add the property "-Doracle.xml.schema/Ignore_Duplicate_components=true" to the server startup script setDomainEnv.cmd.
Starting the Node Manager
To start Node Manager:
  1. Enter the following command:
    (UNIX) DOMAIN_HOME/bin/startNodeManager.sh
    (Windows) DOMAIN_HOME\bin\startNodeManager.cmd
Starting the Administration Server
To start the Administration Server:
  1. Enter the following command:
    (UNIX) DOMAIN_HOME/bin/startWebLogic.sh
    (Windows) DOMAIN_HOME\bin\startWebLogic.cmd
  2. When prompted, enter your user name, password, and the URL of the Administration Server.
Starting the Managed Servers
To start the Managed Servers:
  1. Enter the following command:
    (UNIX) DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url
    (Windows) DOMAIN_HOME\bin\startManagedWebLogic.cmd managed_server_name admin_url
  2. When prompted, enter your user name and password.
Starting Component Processes

When you stopped the Administration Server, you also stopped the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware ControlAfter the upgrade, you will need to restart all of these processes.

  1. Navigate to the DOMAIN_HOME\bin directory.
  2. Execute the following script for each component
    /startComponent.sh component_name

Performing the Upgrade on Host 2

Once you have completed the upgrade on host 1, perform the following steps on each additional host in your environment. Our standard topoloy example includes only two hosts, but you may have more.

Stopping the Components, Servers and Processes on Host 2

You must stop the system components, managed servers and node manager running on Host 2.

Stop the system components first, followed by the managed server(s) and then the node manager. Failure to stop the components in the correct order may result in a failed upgrade.
Stopping System Components

To stop system components, such as Oracle HTTP Server, use the stopComponent script:

Navigate to the DOMAIN_HOME\bin directory and execute the following script for each component:
./stopComponent.sh component_name 
Stopping the Managed Servers
To stop a WebLogic Server Managed Server, use the stopManagedWebLogic script:
  1. Enter the following command:
    (UNIX) DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url
    (Windows)DOMAIN_HOME\bin\stopManagedWebLogic.cmd managed_server_name admin_url
  2. When prompted, enter your user name and password.
    Stop SOA servers and processes in this order:
Stopping the Node Manager

To stop Node Manager, close the command shell/prompt in which it is running.

Alternatively, after having set the nodemanager.properties attribute QuitEnabled to true (the default is false), you can use WLST to connect to Node Manager and shut it down.

Uninstalling the Software

When performing a rolling upgrade, an empty directory is required for installing the new binaries prior to upgrading.

Note:

You must deinstall the upperstack components first, then deinstall JRF. After deinstalling the JRF, back up any remaining files and then delete all files in the directory. The installation directory must be empty.

Follow the instructions in this section to remove the software from the existing ORACLE_HOME. You will reinstall the new software into this same directory.

To start the Oracle Universal Installer in deinstallation mode, execute the following command:

ORACLE_HOME/oui/bin/deinstall.sh

If you want to uninstall the product in a silent (command-line) mode, see Running the Oracle Universal Installer for Silent Uninstallation in Installing Software with the Oracle Universal Installer.

Installing the Software in the Existing Oracle Home

After you have uninstalled the software from the 12c (12.2.1.3) Oracle home, install the 12c (12.2.1.4) binaries into the same Oracle home.

You must install the software on each host in your deployment. Follow the same process that you used to install the software on Host 1. Make sure that you are starting with an empty directory before you begin.

Restarting the Managed Servers and Processes

After the upgrade is complete on Host 2, restart the managed servers.

To start the Managed Servers:
  1. Enter the following command:
    (UNIX) DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url
    (Windows) DOMAIN_HOME\bin\startManagedWebLogic.cmd managed_server_name admin_url
  2. When prompted, enter your user name and password.

Validating the Upgrade

Now that the upgrade is complete on all of the hosts, complete the standard upgrade verification tasks described in this guide to ensure that our components will continue to work as expected.

Note:

Only perform those tasks that pertain to your envivornment, configuration and preferences. These tasks are meant to assist you in verfiying that the upgrade was successful. You may need to perform additional testing based on your configuration.

Recovering from a Failed Upgrade

If your upgrade is unsuccessful, you will need to restore your enviroment from backup. Make sure that you include your backed up configuration and script files. Restore the backup of the Oracle home (on all of the nodes), the entire domain directory (on all of the nodes) and component schemas. In addition, you will need to restore any UI customizations and the applications directory, in addition to domain directory.