Updating the enterprise database

When upgrading the HCL Traveler servers in the HA Pool, it is necessary to upgrade the database schema level of the database used by the HA pool.

If NTS_AUTO_DBSCHEMA has not been set to false in the notes.ini, the HCL Traveler server will automatically update the DB schema as needed. As a result, you can skip the rest of this information.

If NTS_AUTO_DBSCHEMA has been set to false in the notes.ini, then you must manually update the DB schema as part of the HCL Traveler server upgrade process.

Perform the following procedure to manually upgrade the DB Schema:
  1. Determine the current DB Schema level being used by the HCL Traveler HA Servers:
    • On pre-9.0 servers, run the following command: tell traveler sql select * from schemaversion
    • On 9.0 and later releases run this command: tell traveler version
    The Schema version will be in the format version.builddate, for example: 9.0.0.0.20130115.
    Note: In many cases this will not match the HCL Traveler version and build date. Ensure you note the Schema version and not the HCL Traveler version.
  2. Install the Notes® HCL Traveler server on a test system or on the first HCL Traveler system to be upgraded.
  3. From the HCL Traveler server, copy either the file <domino install data dir>\traveler\cfg\db\TravelerSQL.zip or TravelerSQL.tar.gz to the directory <sqldir> on the Enterprise DB server.
  4. Unzip or Untar the TravelerSQL file and CD to the correct directory for your Enterprise DB server (DB2, SQLSERVER, MYSQL, or AS400).
  5. There will be a numbered list of fixup#.sql files. Determine the one which corresponds to the current schema version by looking at the end of the file. Start your search with the fixup#.sql file after the one which contains a statement similar to the following, with the current Schemaversion: 
    UPDATE LNT.schemaversion  SET MAXVERSION='9.0.0.0.20130115';

    For more information on what DDL migration script(s) are needed for upgrading HCL Traveler HA to the latest release, refer to Frequently asked questions about the enterprise database.

  6. Once the correct starting fixup#.sql has been determined, edit the file, as well as all of the following files, and update the Database name, Schema name and path name if you used any value other than the default when creating the database and schema.
  7. Starting with the correct fixup#.sql you located in step 5, execute each fixup#.sql file in order on the DB server using the following commands.

    DB2® on Windows™: db2cmd -c -w -i db2 -tvf fixup#.sql

    DB2® on Linux™ or AIX: db2 -tvf fixup#.sql

    SQL Server: sqlcmd -U <admin_user>-P <admin_password> -i fixup#.sql

    MySQL: mysql -u <admin_user> -p < fixup#.sql

    AS400 Server: RUNSQLSTM SRCSTMF(/QHCL/Proddata/lotus/traveler901/data/traveler/cfg/db/AS400/fixup#.sql) PROCESS(*RUN) NAMING(*SQL) USRPRF(*USER)
    Note: On an AS400 server, you can also copy the fixup#.sql to a local directory on your workstation. Then, select System i Navigator > Databases > Run SQL Scripts, and load and run the fixup#.sql.
  8. Once all fixup#.sql scripts have run, proceed with upgrading the HCL Traveler servers.
  9. Run the appGrants.sql to update permissions for any newly added tables.
  10. Run verifyIndexes.sql to verify the index structure is correct. Some of the statements will show an error if the change has been applied previously. Check the output to confirm that either the change has been applied prior or a statement passed.
    Note: On MySQL database, execute verifyIndexes.sql with --force option. Without --force option, the command will stop on the first failure. For example, mysql -u <admin_user> -p < verifyIndexes.sql --force.