1. Upgrading Oracle HTTP Server
  2. About the Reduced Downtime Upgrade Process
  3. Performing a Reduced Downtime Upgrade

Performing a Reduced Downtime Upgrade

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

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 two 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 the upgrade. In addition, Oracle recommends that you create a backup of UI customizations and the applications directory, in addition to domain directory. See Creating a Complete Backup.
  • 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 the 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.

Parent topic: About the Reduced Downtime Upgrade Process

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.

Parent topic: Performing a Reduced Downtime Upgrade

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

Parent topic: Performing the Upgrade on Host 1

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:

This task applies only to standalone Oracle HTTP Server. You cannot uninstall Oracle HTTP Server when it is collocated in a WebLogic Server domain, as partial deconfiguration of a configured domain is not supported.

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:

UNIX: ORACLE_HOME/oui/bin/deinstall.sh

Windows: ORACLE_HOME\oui\bin\deinstall.cmd

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.

Parent topic: Performing the Upgrade on Host 1

Installing the Product Distributions

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.

Note:

When Infrastructure is required for the upgrade, you must install the Oracle Fusion Middleware distribution first before you install other Fusion Middleware products.
Before you begin, note the following:

  • Make sure that you have uninstalled the existing product distributions before installing the 12c (12.2.1.4.0) distributions.

  • Use the same install path (Oracle home) for the installation of the new distributions that you used for the previous distributions that you uninstalled.
To install the 12c (12.2.1.4.0) distributions:
  1. Sign in to the target system.
  2. Download the following from Oracle Technology Network or Oracle Software Delivery Cloud to your target system:
    • Oracle Fusion Middleware Infrastructure (fmw_12.2.1.4.0_infrastructure_generic.jar)
    • Oracle HTTP Server (UNIX: fmw_12.2.1.4.0_ohs_linux64.bin), (Windows: setup_fmw_12.2.1.4.0_ohs_win64.exe)
  3. Check that your machines meet the following requirements:
    • Ensure that the system, patch, kernel, and other requirements are met as specified in Installing and Configuring Oracle HTTP Server.
    • Because Oracle HTTP Server is installed by default on port 7777, you must ensure that port 7777 is not used by any service on the nodes. To check if this port is in use, run the following command before you install Oracle HTTP Server. You must free the port if it is in use.

      netstat -an | grep 7777

  4. On UNIX platforms, if the /etc/oraInst.loc file exists, check that its contents are correct. Specifically, check that the inventory directory is correct and that you have write permissions for that directory.
    If the /etc/oraInst.loc file does not exist, you can skip this step.
  5. Change to the directory where you downloaded the 12c (12.2.1.4.0) product distribution.
  6. 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
  7. 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.
  8. On the Welcome screen, review the information to make sure that you have met all the prerequisites. Click Next.
  9. 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.
  10. On the Installation Location screen, specify the location for the Oracle home directory and click Next.
    Since you are installing the standard installation topology for a collocated Oracle HTTP Server in a WebLogic Server domain, enter the path to an existing Oracle Fusion Middleware Infrastructure Oracle home.
    See Selecting Directories for Installation and Configuration in Planning an Installation of Oracle Fusion Middleware.
  11. On the Installation Type screen, select the following:
    • For Infrastructure, select Fusion Middleware Infrastructure
    • For Oracle HTTP Server, select Collocated HTTP Server (Managed through WebLogic Server)
    Click Next.
  12. 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).
  13. 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.

  14. On the Installation Progress screen, when the progress bar displays 100%, click Finish to dismiss the installer, or click Next to see a summary.
  15. 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.
  16. After you have installed Oracle Fusion Middleware Infrastructure, enter the following command to start the installer for your product distribution and repeat the steps above to navigate through the installer screens:
    (UNIX) ./fmw_12.2.1.4.0_ohs_linux64.bin
    (Windows) setup_fmw_12.2.1.4.0_ohs_win64.exe
You have installed the Oracle HTTP Server in a collocated mode.

Parent topic: Performing the Upgrade on Host 1

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.

Parent topic: Performing the Upgrade on Host 1

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.

Parent topic: Performing a Reduced Downtime Upgrade

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.

Parent topic: Performing the Upgrade on Host 2

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:

This task applies only to standalone Oracle HTTP Server. You cannot uninstall Oracle HTTP Server when it is collocated in a WebLogic Server domain, as partial deconfiguration of a configured domain is not supported.

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:

UNIX: ORACLE_HOME/oui/bin/deinstall.sh

Windows: ORACLE_HOME\oui\bin\deinstall.cmd

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.

Parent topic: Performing the Upgrade on Host 2

Installing the Software into the Existing Middleware Home

Install the software into the empty Middleware home.

Uninstall the software from the existing Oracle home before installing the 12c (12.2.1.4.0) product distributions. Install the software using the same process you used to install on Host 1.

Parent topic: Performing the Upgrade on Host 2

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.

Parent topic: Performing the Upgrade on Host 2

Validating the Upgrade

After you have completet the upgrade on all hosts, complete the standard upgrade verification tasks to ensure that all components will continue to work as expected.

See Tasks to Perform After Upgrade.

Note:

Only perform those tasks that pertain to your environment, 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 environment 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.

Parent topic: Performing a Reduced Downtime Upgrade