IBM Support

IV86831 TWS 9.3 FP2 installation failure with Oracle db

Troubleshooting


Problem

TWS 9.3 FP2 installation can fails on AIX ,HP,Linux390 ,linuxppc with Oracle DB. The issue is due to the fact that on that platform Installation Manager at 32 bit could be present and if the Oracle DB is at 64 bit level the TWS upgrade tool to update the TWS schema can fails in that condition.

Symptom

<message>The following errors were generated while updating.

11:25:08 AM: AWSJIM405E: Verify you executed IBM Installation Manager from a shell
with the ORACLE_HOME environment variable correctly set, and ensure you
added the Oracle native client libraries located in $ORACLE_HOME/lib to
your LIBPATH environment variable.

Internal error is:
java.lang.UnsatisfiedLinkError: ocijdbc11 ( 0509-022 Cannot load module
/app/oracle/product/11GR2_TWS/lib/libocijdbc11.so.
0509-026 System error: Cannot run a file that does not have a valid
format.)class java.lang.UnsatisfiedLinkErrornullocijdbc11 ( 0509-022
Cannot load module /app/oracle/product/11GR2_TWS/lib/libocijdbc11.so.
0509-026 System error: Cannot run a file that does not have a valid
format.)java.lang.ClassLoader.loadLibraryWithPath(ClassLoader.java:1231)
java.lang.ClassLoader.loadLibraryWithClassLoader(ClassLoader.java:1195)
java.lang.System.loadLibrary(System.java:530)
oracle.jdbc.driver.T2CConnection$1.run(T2CConnection.java:3535)

Environment

Install Manager at 32 bit is present with oracle 64 bit.

Diagnosing The Problem

Check that IM is at 32 bit with the command:

for eg:


file /opt/ibm/InstallationManager/eclipse/IBMIM
or the home install directory of InstallationManager/eclipse/IBMIM

and verify that your Oracle is at 64 bit.for eg

file against
libocijdbc11.so

Resolving The Problem

For Installation performed with TWS MDM 9.3 fp2 packages downloaded before the 2nd August:


Point 1) Manually update the TWS DB schema using the upgrade tool provided
with TWS 9.3 FP2 package forcing the jdbc driver to type 4 and changing
some parameters in properties file (see below)

Point 2) Set the IM property -DskipDbConfig=true so the TWS install will not
perform the db upgrade.

For Point 1.

Refer to TWS 9.2 FP2 readme file "Updating or upgrading the database
schema for DB2 or Oracle"
changing the following item into file upgradeOracleIWSDB.properties:
- add the key JDBC_DRIVER_TYPE=4
- set also the fields DB_HOSTNAME, PORT, DB_NAME (please ignore the
sentence that they are valid only for Solaris these are needed also for
other interp).
- Check that the upgrade tool will work with this change . Set the key
UPGRADE_DB=FALSE and then run it.In that way the tool will do nothing on
TWS DB schema but
will generate in the screen the sql statments.If no error will be
displayed move on next step.
- Set UPGRADE_DB=TRUE and launch the db upgrade tool.

For Point 2.

- Set the IM property -DskipDbConfig=true into file
/opt/IBM/InstallationManager/eclipse/IBMIM.ini
- Run TWS 9.3 FP2 update with IM running
/opt/IBM/InstallationManager/eclipse/IBMIM


----------------------------------------------------------------------------------------------------

From August 2nd these packages for 9.3 FP2 MDM has been refreshed into FixCentral site including the fix for apar IV86831. Customer can download these packages and the issue is solved. list of packages:


9.3.0-IBM-IWS-HPIA64-FP0002
9.3.0-IBM-IWS-LINUXPPC-FP0002
9.3.0-IBM-IWS-SOLARIS_I386-FP0002
9.3.0-IBM-IWS-LINUX390-FP0002
9.3.0-IBM-IWS-AIX-FP0002
9.3.0-IBM-IWS-LINUX_X86_64-FP0002
9.3.0-IBM-IWS-WINDOWS_X86_64-FP0002









[{"Product":{"code":"SSGSPN","label":"IBM Workload Scheduler"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Not Applicable","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"}],"Version":"9.3","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg21987299