Troubleshooting the installation of HCL Traveler on IBM® i

You may run into unique problems while installing HCL Traveler on IBM i systems.

Problem

After upgrading Domino for an existing Traveler server on an IBM i system system with an HA configuration, the Traveler server may not start with the following console message:

HTTP JVM: Unable to load Java Database Connectivity (JDBC) driver named com.ibm.as400.access.AS400JDBCDriver
Verify that the jar /QIBM/PRODDATA/LOTUS/DOMINO110000/Traveler/lib/jt400.jar is installed properly
NTS_DBPath specifies the correct jar

CAUSE

Upgrading Domino changed the location used for finding the jt400.jar.

RESOLUTION

After upgrading Domino, validate the jt400.jar and the NTS_DBPATH value in notes.ini are correct.

Note: See the Configuring the HCL Traveler High Availability pool on IBM iarticle for more information

Problem

After installing Traveler 9.0.1.15 on IBM i system with an HA configuration, the first startup of the HCL Traveler server will fail during the DB schema upgrade to version 20160812 with the following console message:

Traveler: Upgrading HCL Traveler Database schema from version 20160726 to version 20160812
Traveler: SEVERE  *system Unknown Database exception thrown at startup, attempting startup anyways. Exception Thrown: com.lotus.sync.db.PersistenceException: java.sql.SQLException: [SQL0952] ocessing of the SQL statement ended.  Reason code 10. (SQLState: 57014 ErrorCode: -95 
Traveler: SEVERE  *system  Exception Thrown: com.lotus.sync.db.PersistenceException: java.sql.SQLException: [SQL0952] Processing of the SQL statement ended.  Reason code 10. (SQLState: 57014 ErrorCode: -95 
Traveler: Server stopping for PID 3,381 ...
Traveler: Server stopped.

CAUSE:

The DB2 on IBM i server is returning a warning (inquiry message) because of possible data loss, requesting that the client Cancel or Ignore the requested operation. Because this request over JDBC requires an interactive response (typing 'I' to ignore), the server returns an Error Code: -952 with SQLState: 57014 and Reason code 10.

Note: In this case, Traveler is performing an "Add NOT NULL constraint" operation for some tables using the ALERT TABLE SQL statement.

RESOLUTION:

On DB2 for IBM i, change the message description default value to 'I' by running the following CL command:

CHGMSGD MSGID(CPA32B2) MSGF(QSYS/QCPFMSG) DFT('I')

Then restart the Traveler server.

Note: After the server completes the schema upgrade, you can change the message description default value back by running the following CL command:

CHGMSGD MSGID(CPA32B2) MSGF(QSYS/QCPFMSG) DFT('C')