IBM Traveler Derby Database Corruption

After an OS restart we encountered a problem with the Traveler Server, the local Derby database became corrupt, and therefore Traveler clients could not sync the enterprise data.

After starting the Traveler task the following errors were logged in the console:

\[09C4:000C-0B5C\]    Traveler: WARNING Session ID d082448615552a82da8175a9ea5d071a309 could not be associated with any existing PS threads.

\[09C4:000C-0B5C\]    Traveler: SEVERE    Exception Thrown: com.lotus.sync.db.PersistenceException: java.sql.SQLSyntaxErrorException: Invalid Properties list in FROM list.  There is no index ‘IDX_GUIDNEXT_1’ on table ‘GU

\[09C4:000C-0B5C\]    Traveler: WARNING Sync exception being treated as a backend failure. Exception Thrown: com.lotus.sync.db.PersistenceException: java.sql.SQLSyntaxErrorException: Invalid Properties list in FROM list.

Next course of action was to try to defrag the Database which solved the problem. I simply removed the Traveler task from the “notes.ini” file and started it with “Load Traveler -defrag” command. The defragmentation Process took about 10 Minutes after which the Traveler task was started and the mobile devices could sync the PIM Data without any problems.

The following article from IBM also describes a similar behavior:

http://www-01.ibm.com/support/docview.wss?uid=swg21608001