Unable to create the sub-directories for the history
directory.
The sub-directories for the history directory cannot be created
because the SSM cannot find the executable file named symmkdir which
is required to create these sub-directories.
This fix applies
only to Linux x86_64 platform.
Readme
file for: IBM® Platform
Symphony
Product
Release: 7.1.1
Update
Name: Interim Fix 435401
Fix ID: sym-7.1.1-build435401-ms
Publication
date: December 23 2016
Last
modified date: December 23 2016
APAR: P102045
Download this fix
from the following location:
http://www.ibm.com/eserver/support/fixes/
Product: Platform Symphony
Component Name:
SOAM
Apply this fix if
you have Platform Symphony 7.1.1 and fix 413386 installed.
1. Disable all applications and stop the SD service
Log
on to the master host as the cluster administrator and run:
> source $EGO_TOP/profile.platform
> egosh user logon -u Admin -x Admin
> soamcontrol app disable all
> egosh service stop SD
2.
Back up
files
Back up the
following files on management hosts:
1.
Log on to management hosts
in the cluster and decompress the pssasetup2015_linux-x86_64_build435401.tar.gz package
> tar zxfo pssasetup2015_linux-x86_64_build435401.tar.gz -C $EGO_TOP
Option 1: Use a wrapper to start
the SSM
Export the following environment
variable before executing the SSM start command:
> export SOAM_SERVERDIR=<Server_Installtion_Directory>
1. Verify the installation
Run:
> ssm -V
The
following is an example output of successfully running the command:
IBM Platform Symphony 7.1.1.0 build 435401, Dec 16 2016
Copyright International Business Machines Corp, 2001-2015.
US Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.
2. Start the SD service and enable applications
Log on to the master host as the cluster administrator
and run:
> source $EGO_TOP/profile.platform
> egosh user logon -u Admin -x Admin
> egosh service start SD
> soamcontrol app enable $AppName
1. Disable all applications and stop the SD service
Log on to the master host as the cluster administrator
and run:
> source $EGO_TOP/profile.platform
> egosh user logon -u Admin -x Admin
> soamcontrol app disable all
> egosh service stop SD
2. Remove configuration for starting SSM
If you used a wrapper to start the SSM
Remove the following
environment variable before executing the SSM start command:
> export SOAM_SERVERDIR=<Server_Installtion_Directory>
3.
Log on
to management hosts in the cluster and restore the backup files for the
following binaries:
> $EGO_TOP/soam/7.1.1/linux-x86_64/etc/sd
> $EGO_TOP/soam/7.1.1/linux-x86_64/etc/ssm
4. Start the SD service and enable the application
Log on to the master host as the cluster administrator and run:
> source $EGO_TOP/profile.platform
> egosh user logon -u Admin -x Admin
> egosh service start SD
> soamcontrol app enable $AppName
sd
ssm
© Copyright IBM Corporation 2016
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.