Traveler 9.0.1.8 refuses to reload. Out of nowhere. After a reboot of server, this error occurs on restart with load traveler -defrag

This error occurs on restart of Traveler. Command Load traveler -defrag

09-11-2020 12:08:28 Remote console command issued by xxxxxxxxxxxxx: load traveler -defrag
09-11-2020 12:08:28 IBM Traveler: Starting JVM with Maximum Memory = 6144M based on maximum of 1/4 of physical memory (24576M) or the Maximum Memory Size specified in the server document (512M)
09-11-2020 12:08:29 Traveler: Server starting...
09-11-2020 12:08:31 Traveler: Traveler: --- Performing Database Maintenance ---
09-11-2020 12:08:32 Traveler: SEVERE *system Exception Thrown: java.sql.SQLException: The conglomerate (315.424) requested does not exist.

09-11-2020 12:08:32 Traveler: SEVERE *system Exception Thrown: java.sql.SQLException: The conglomerate (315.440) requested does not exist.

09-11-2020 12:08:32 Traveler: SEVERE *system Exception Thrown: java.sql.SQLException: The conglomerate (315.456) requested does not exist.

09-11-2020 12:08:32 Traveler: SEVERE *system Exception Thrown: java.sql.SQLException: The conglomerate (315.953) requested does not exist.

09-11-2020 12:08:32 Traveler: SEVERE *system Exception Thrown: java.sql.SQLException: The conglomerate (316.129) requested does not exist.

09-11-2020 12:08:32 Traveler: SEVERE *system exception caught attempting to clear warnings Exception Thrown: java.sql.SQLNonTransientConnectionException: No current connection.

09-11-2020 12:08:32 Traveler: SEVERE *system Error rollingback TransactionID=38 Error State: 08003 Error Code: 40000 Exception Thrown: java.sql.SQLNonTransientConnectionException: No current connection.

09-11-2020 12:08:32 Traveler: SEVERE *system Exception caught executing database maintenance. com.lotus.sync.db.PersistenceException: java.sql.SQLException: Java exception: 'Index: 2, Size: 2: java.lang.IndexOutOfBoundsException'. (SQLState: XJ001 ErrorCode: 0)

09-11-2020 12:08:32 Traveler: SEVERE *system Error trying to initialize LotusTraveler Domino database Exception Thrown: com.lotus.sync.db.PersistenceException: java.sql.SQLException: The conglomerate (315.424) requested does not exist. (SQLState: XSAI2 ErrorCode: 30000)

09-11-2020 12:08:32 Traveler: SEVERE *system Error getting listener count Exception Thrown: com.lotus.sync.db.PersistenceException: java.sql.SQLSyntaxErrorException: Invalid Properties list in FROM list. There is no index 'IDX_PUSH_3' on table 'PUSH'.

09-11-2020 12:08:33 Traveler: SEVERE *system Exception Thrown: com.lotus.sync.db.PersistenceException: java.sql.SQLSyntaxErrorException: Invalid Properties list in FROM list. There is no index 'IDX_PUSH_3' on table 'PUSH'.

09-11-2020 12:08:33 Traveler: SEVERE *system The component CAF could not be started. Internal error: java.lang.RuntimeException: Listener Store: called when not running Exception Thrown: java.lang.RuntimeException: Listener Store: called when not running

09-11-2020 12:08:33 Traveler: Server stopping for PID 6.668 ...
09-11-2020 12:08:37 Traveler: Server stopped.

Hello,

have you tried to start traveler without defrag?

If it starts, then please run "tell traveler tablerepair show *" and paste output here.

9.0.1.8 is a very old Traveler version, so it is hard to say - will this command work...

If there is a small amount of users, you can try backup & remove Data/ntsdb folder. Users will lose all device information and will have to perform initial sync/authorization, but at least Traveler should start.

Though this should be used unless absolutely necessary

Agree with Aleksandr, 9.0.1.8 is very old.

You might want to consider upgrading to the latest version of Traveler as a lot of fixes has been added to it since your current version.

Recommended maintenance for Traveler
https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0036438&sys_kb_id=07b23202db89189055f38d6d13961963

Definitely agree with Jessie that you need to upgrade. However, it is unlikely that this will help you walk out of your current situation. It is likely that the derby database (ntsdb) has become corrupted. As already mentioned above, you can remove the ntsdb folder. The database will be recreated on startup. Devices will have to resync plus if you use device approval, devices will need to be re-approved.