So IBM Traveler 9.0.1.16 is now available.  We've been waiting on it to upgrade our internal server that was on an older version, mostly due to the issue that Detlev posted about in December.  That is "fixed" in this release, however my experience upgrading revealed that it wasn't so much fixed as the command that you need to issue to resolve the error was enabled for use.

So, after upgrading Traveler from the .12 release, the server started up and watched as the Traveler db had its design updated and also saw updates to the Derby database used by Traveler getting logged:

02/16/2017 05:19:42 PM Traveler: Server starting...
02/16/2017 05:19:56 PM Traveler: GUIDMAP has no records violating the constraint.
02/16/2017 05:19:56 PM Traveler: Primary key PK_GUIDMAP successfully created.
02/16/2017 05:19:56 PM Traveler: GUIDMAP table is repaired.
02/16/2017 05:19:56 PM Traveler: TS_FILTERS has no violating records.
02/16/2017 05:19:56 PM Traveler: Primary key PK_TSFILTERS successfully created.
02/16/2017 05:19:56 PM Traveler: TS_FILTERS table is repaired.
02/16/2017 05:19:56 PM Traveler: PUSH has no violating records.
02/16/2017 05:19:56 PM Traveler: Primary key PK_PUSH successfully created.
02/16/2017 05:19:56 PM Traveler: PUSH table is repaired.
02/16/2017 05:19:56 PM Traveler: REPLICAS has no violating records.
02/16/2017 05:19:56 PM Traveler: Primary key PK_REPLICAS successfully created.
02/16/2017 05:19:56 PM Traveler: REPLICAS table is repaired.

However, after that was done, I saw the message Detlev wrote about:

02/16/2017 05:20:00 PM Traveler: WARNING *system Exception caught trying to create constraint PK_INVMAP on Table INV_MAP. Exception Thrown: com.lotus.sync.db.PersistenceException: java.sql.SQLSyntaxErrorException: 'DEVUID' cannot be a column of a primary key because it can contain null values.

I wasn't expecting this, but figured I could try the command IBM gave out with the Hotfix:

tell traveler sql ALTER TABLE inv_map ALTER COLUMN devuid NOT NULL

After restarting HTTP, the error did not appear again, so it looks like running this command may be necessary if you are upgrading your standalone Traveler install from an older release.

Of course, as always, YMMV.

I'll be at the IBM Connect conference next week - hope to see some of you there!

Donate to support Cystic Fibrosis research for a cure

comments powered by Disqus