fighting for truth, justice, and a kick-butt lotus notes experience.

 
alt

Detlev Poettgen

 

Hotfix via PMR available for Traveler 9.0.1.15 Standalone issue regarding INV_MAP table

 2 Dezember 2016 11:10:40
After upgrading our IBM Traveler 9.0.1.15 Standalone server, you can get this error messages on the console :

02.12.2016 08:49:19   Traveler: Server starting...
02.12.2016 08:49:33   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 or unique key because it can contain null


After opening a PMR, we received a Hotfix today :

FIX VERSION:      9.0.1.15
  FIX BUILD LEVEL:  201611291200_40

  FIX LIST:

   - LO90903: DUPLICATE ACCOUNT RECORDS WHERE THE ACCOUNT NAME CHARACTERS ARE IN VARIOUS LETTER CASE ARE NOT IDENTIFIED BY DBACCOUNTSCHECK
   - LO90926: STANDALONE TRAVELER SERVERS WITH INCORRECT DATABASE SCHEMA NEED AN ADDITIONAL SCHEMA MANAGEMENT METHOD FROM THE TRAVELER SERVER.

You need this Hotfix and after installing the fix you will have to run:

tell traveler sql ALTER TABLE inv_map ALTER COLUMN devuid NOT NULL

So if you are running Traveler in Standalone mode, you should wait with your Traveler update to 9.0.1.15 until the Hotfix is public available or should open a PMR to get it.

Same issue and hotfix was reported here, too: http://atnotes.de/index.php/topic,60514.0.html



Kommentare

1Julian  06.12.2016 15:20:43  Hotfix via PMR available for Traveler 9.0.1.15 Standalone issue regarding INV_MAP table

Hi Detlev

So that means that we should be able to upgrade our HADR configured Traveler Server without headache?

Tx

Julian