Readme
for IBM® Spectrum Conductor with Spark 2.2.0.0 Interim Fix 455575
Readme
file for: IBM Spectrum Conductor with Spark
Product/Component
Release: 2.2.0.0
Update
Name: Interim
Fix 455575
Fix
ID: cws-2.2-build455575
Publication
date: June 7, 2017
Abstract
Vemkd core dump with the exclusive consumers feature.
Description
This interim fix resolves the vemkd
core dump issue in IBM Spectrum Conductor with Spark v2.2.0.0. This issue
occurs when assign/un-assign a resource group to/from a consumer after the
exclusive consumers feature is enabled.
Contents
1. List of fixes
2. Download location
3. Products or components
affected
4. Installation and
configuration
5. List of files
6. Copyright and trademark
information
1. List of fixes
APAR: P102246
2. Download location
Download
Fix 455575 from the following location: http://www.ibm.com/eserver/support/fixes/
3. Products or components
affected
Product/Component Name, Platform, Fix ID:
Spectrum Conductor with Spark/EGO, Linux 64-bit,
cws-2.2-build455575
4. Installation and
configuration
System requirements
Linux x86_64
Before installation
1.
Stop the cluster. Log on to the management host as
the cluster administrator and run:
>
egosh service stop all
>
egosh ego shutdown all
2.
For recovery purposes, back up the following files
(which are replaced by this interim fix) to another directory:
$EGO_TOP/3.5/linux-x86_64/etc/vemkd
$EGO_TOP/3.5/linux-x86_64/lib/policy/libslot.so
Installation
1.
Log on to all management hosts in your cluster as the cluster
administrator and decompress the cws-2.2.0.0_x86_64_build455575.tar.gz file
to the directory where you installed IBM Spectrum Conductor with Spark:
>
tar zxfo
cws-2.2.0.0_x86_64_build455575.tar.gz
-C $EGO_TOP
After installation
1. Verify
the installation by running the vemkd -V
command. The following is a sample output of successfully running this command:
> vemkd -V
EGO 3.5.0
build 455575, May 31 2017
binary type: linux-x86_64
notes:
fixes:
2. Start the cluster. Log on to the
management host as the cluster administrator and run:
> egosh
ego start all
Uninstallation (if required)
1.
Stop the cluster. Log on to the management host as
the cluster administrator and run:
>
egosh service stop all
>
egosh ego shutdown all
2.
Log
on to all management hosts in the cluster and restore the backup for the
following files:
$EGO_TOP/3.5/linux-x86_64/etc/vemkd
$EGO_TOP/3.5/linux-x86_64/lib/policy/libslot.so
3. Start the cluster. Log on to the
management host as the cluster administrator and run:
> egosh
ego start all
5. List of files
vemkd, libslot.so
6. Copyright and trademark
information
©
Copyright IBM Corporation 2017
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.