Readme for IBM® Spectrum Conductor 2.5.0 RFE 151866

Readme file for: IBM Spectrum Conductor
Product/Component release: 2.5.0
Fix ID:
sc-2.5-build600663
Publication date: September 1, 2021

This enhancement enables you to upgrade the IBM Java Runtime Environment (JRE) in IBM Spectrum Conductor 2.5.0 to JRE 8 SR6 FP35.

 

Contents

1.        Download location 

2.        Installation and configuration

3.        Uninstallation

4.        List of files

5.        Product notifications

6.        Copyright and trademark information

 

1.   Download location

Download enhancement 600663 from the following location: http://www.ibm.com/eserver/support/fixes/

2.   Installation and configuration

Follow the instructions in this section to download and install this enhancement to your cluster.

System requirements

·       Linux x86_64 or Linux ppc64le

·       RPM version 4.2.1 or later must be installed on each host in the cluster

Installation

a.        Log in to the cluster management console as the cluster administrator and stop all instance groups.

b.        Log on to the primary host as the cluster administrator:

> egosh user logon -u Admin -x Admin

c.        Stop all services and shut down the cluster:

> egosh service stop all

> egosh ego shutdown all

d.        Log on to each host in your cluster with root or sudo-to-root permission. This JRE upgrade is mandatory on all hosts that handle workload; therefore, upgrade on all management hosts, and on any compute hosts that handle workload.

e.        Define the CLUSTERADMIN environment variable and set it to any valid operating user account, which then owns all installation files, for example: 

> export CLUSTERADMIN=egoadmin

f.         Upgrade the JRE by using the .rpm file in this enhancement (this step requires RPM version 4.2.1 or later to be installed on the host):

> rpm -ivh --replacefiles --prefix $EGO_TOP --dbpath dbpath_location egojre-8.0.6.35.os_type.rpm

    where $EGO_TOP specifies the path to where the cluster is installed, dbpath_location specifies the path to your database, and os_type is either x86_64 or ppc64le.

g.        Source the cluster profile again and start the cluster: 

> egosh ego start all

The cshrc.jre and profile.jre files are updated to the current JRE version. If you made copies of these files, ensure that you update the copied files with the new JRE version.

h.        Log in to the cluster management console as the cluster administrator and start the required instance groups.

        Tip: Instance groups that were previously deployed before this fix will reference the old JAVA_HOME in the $SPARK_HOME/conf/spark-env.sh until the value is updated. This value can be set in the Spark configuration parameters of the instance group, see the IBM Documentation Configuring Spark versions for an instance group topic. Instance groups deployed after you apply this fix receive the new JAVA_HOME location.

i.         Run the rpm –qa command to verify the installation:

> rpm -qa --dbpath dbpath_location |grep egojre

egojre-8.0.6.35-600663.os_type

where dbpath_location specifies the path to your database, and os_type is either x86_64 or ppc64le.

3.   Uninstallation

If required, follow the instructions in this section to uninstall this enhancement from your cluster.

a.     Log in to the cluster management console as the cluster administrator and stop all instance groups.

b.     Log on to the primary host as the cluster administrator:

> egosh user logon -u Admin -x Admin

c.     Stop services and shut down the cluster:

> egosh service stop all

> egosh ego shutdown all

d.     Log on to each upgraded host in your cluster with root or sudo-to-root permission.

e.     Define the CLUSTERADMIN environment variable and set it to any valid operating user account, which then owns all installation files, for example: 

> export CLUSTERADMIN=egoadmin

f.      Uninstall the existing JRE and install the old JRE (this step requires RPM version 4.2.1 or later to be installed on the host):

> rpm -e egojre-8.0.6.35-600663.os_type --dbpath dbpath_location --nodeps

    where os_type is either x86_64 or ppc64le and dbpath_location specifies the path to your database.

> rpm -qa --dbpath dbpath_location |grep egojre

For each previous egojre .rpm package, run:

> rpm -e egojre_name --dbpath dbpath_location --nodeps

Then, install the old JRE:

> mkdir -p /tmp/extract250

> conductor2.5.0.0_os_type.bin --extract /tmp/extract250

> rpm -ivh --prefix $EGO_TOP --dbpath dbpath_location /tmp/extract250/egojre-*.rpm

    where os_type is either x86_64 or ppc64le, $EGO_TOP specifies the path to where the cluster is installed, and dbpath_location specifies the path to your database.

g.     Source the cluster profile again and start the cluster:

> egosh ego start all

h.     Log in to the cluster management console as the cluster administrator and start the required instance groups.

4.   List of files 

egojre-8.0.6.35.x86_64.rpm

egojre-8.0.6.35.ppc64le.rpm

5.   Product notifications

To receive information about product solution and patch updates automatically, subscribe to product notifications on the My Notifications page http://www.ibm.com/support/mynotifications/ on the IBM Support website (http://support.ibm.com). You can edit your subscription settings to choose the types of information you want to get notification about, for example, security bulletins, fixes, troubleshooting, and product enhancements or documentation changes. 

6.   Copyright and trademark information 

© Copyright IBM Corporation 2021

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM®, the IBM logo and ibm.com® are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.