Attempting to configure the TEPS on Linux platforms results in the following error message:
"InstallPresentation.sh completion code 139"
Error is encountered when the bit level of Tivoli Enterprise Portal Server (TEPS) binary does not match the bit level of the DB2 instance.
Diagnosing the problem
Review the most recent TEPS RAS log ($CANDLEHOME/logs/<hostname>_cq_KfwServices_5*-01.log).
Error seen in TEPS RAS log:
(51D2F852.002C-1:kglcry.c,445,"checkICCStatus") ICC unknown error detected
(51D2F852.002D-1:kglcry.c,396,"printICCStatus") ICC Status for majRC=majRC is unknown (999), minRC=minRC is unknown (999), mode=FIPS mode is unknown (999)
(51D2F852.002E-1:kglcry.c,398,"printICCStatus") ICC Status desc=/opt/IBM/ITM/li6243/gs/icc/icclib/libicclib.so: cannot open shared object file: No such file or directory
(51D2F852.002F-1:kglcry.c,2567,"initializeICC") ICC initialization failed
(51D2F852.0030-1:kglcry.c,2790,"CRY_Encrypt") Function failed with error code 37
Confirm bit of TEPS binary:
# cd $CANDLEHOME
# file `find . -name KfwServices`
Confirm bit of DB2 Instance:
# Switch user to the DB2 Instance owner
su - <DB2 Instance Owner>
# Use the db2level command to confirm bit level of DB2 product
DB21085I Instance "db2inst1" uses "64" bits and DB2 code release "SQL10010"
with level identifier "0201010E".
Informational tokens are "DB2 v10.1.0.0", "s120403", "LINUXAMD64101", and Fix Pack "0".
Product is installed at "/opt/ibm/db2".
When running DB2 9.5 or higher, the instance bit size is determined by the operating system where the DB2 product is installed.
Resolving the problem
When the DB2 Instance is 64-bit, the TEPS must be installed using the 64-bit version of IBM Tivoli Monitoring.
When the DB2 Instance is 32-bit, the TEPS must be installed using the 32-bit version of IBM Tivoli Monitoring.