Go to main content

Updating Your Oracle® Solaris Cluster 4.4 Environment

Exit Print View

Updated: March 2019
 
 

How to Confirm Your Oracle Solaris Bundled Application is Supported

Check the following list to see if your application is supported in Oracle Solaris 11.4. See http://www.oracle.com/technetwork/systems/end-of-notices/eonsolaris11-392732.html.

  • Depending if your application is supported, or not, perform one of the following tasks.
    • If your application with the version you are running is supported, proceed to Choosing an Oracle Solaris Cluster Update Method.
    • If your application with the version you are running is not supported, but a newer version is supported in Oracle Solaris 11.4, perform these steps.

      See http://www.oracle.com/technetwork/systems/end-of-notices/eonsolaris11-392732.html.


      Note -  For applications bundled with Oracle Solaris, the upgrade to Oracle Solaris 11.4 will remove the unsupported application version and will install new application version if one is supported on Oracle Solaris 11.4.
      1. Confirm the new version is supported by Oracle Solaris Cluster 4.4.

        See the Oracle Solaris Cluster 4.4 Compatibility Guide.

      2. Make a backup of your boot environment so you can return to the current configuration if needed.
      3. It may be that configuration changes will be required at the application configuration level and the cluster configuration to support the new version once the cluster boots into Oracle Solaris 11.4. One such case is when application configuration and or cluster configuration refers to application locations and these locations change. If your configuration will require changes perform these steps, otherwise proceed to Choosing an Oracle Solaris Cluster Update Method.
        1. Suspend each resource group(s) that manage the application that is getting a newer version in Oracle Solaris 11.4.
          # clresourcegroup suspend resource-group

          The resource groups remain online but they are prevented from failing the application over during upgrade. While in this state, the resource groups are also prevented from automatically rebooting the application when the nodes are rebooted after upgrade.

        2. Perform the upgrade on the nodes. Proceed to Choosing an Oracle Solaris Cluster Update Method.

          Perform all steps, including booting into the new boot environment. Then return to this procedure.

        3. Disable each resource for the application that got a newer version in Oracle Solaris 11.4.
          # clresource disable resource

          Disabling this resource ensures that the resource does not attempt to start before necessary configuration updates are done.

        4. For each resource group that you recorded in the first step, bring the resource group online.
          # clresourcegroup online resource-group

          This step brings online necessary storage resources and other resources that this resource depends on.

        5. Make necessary updates to the configuration to reflect the new software version.

          For example, upgrading from Oracle Solaris 11.3 to Oracle Solaris 11.4 removes Apache 2.2 and installs Apache 2.4. After booting into Oracle Solaris 11.4, both apachectl and httpd.conf may point to /etc/apache2/2.2, /var/apache2/2.2 or /usr/apache2/2.2. All of which will be gone after the node upgrade to Oracle Solaris 11.4. After the upgrade, update configuration files and resource properties with changes required to point to Apache 4.4 locations.

        6. Enable each resource that you disabled earlier in this procedure.
    • If there is no new version of your application supported in Oracle Solaris 11.4, and it will not be supported in a future release, perform these steps.
      1. Make a backup of your boot environment so you can return to the current configuration if needed.
      2. Remove all cluster objects for this application (resources, resource groups and protection groups).

        Note -  For applications bundled with Oracle Solaris 11.4, the upgrade to Oracle Solaris 11.4 will remove the unsupported application.
      3. Proceed to Choosing an Oracle Solaris Cluster Update Method.
    • If there is no new version of your application supported in Oracle Solaris 11.4, and it will be supported in the future by Oracle Solaris 11.4, perform these steps.

      Note -  For applications bundled with Oracle Solaris 11.4, the upgrade to Oracle Solaris 11.4 will remove the unsupported application.
      1. Make a backup of your boot environment so you can return to the current configuration if needed.
      2. Remove all cluster objects for this application (resources, resource groups and protection groups).
      3. Disable the application so that it does not attempt to start when the nodes are booted into Oracle Solaris 11.4 boot environment.
      4. Proceed to Choosing an Oracle Solaris Cluster Update Method.