Troubleshooting the installation of IBM® Traveler on IBM® i
You may run into unique problems while installing IBM Traveler on IBM i systems.
PROBLEM:
After installing Traveler 9.0.1.15 on IBM i system with an HA configuration, the first startup of
the IBM Traveler server will fail during the DB schema upgrade to version 20160812 with the
following console
message:
Traveler: Upgrading IBM 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')