Method 1
Inspect the flow_all_log.log file on the Flow server, which can be found in this directory: C:\Program Files\Donnelley\MultiTrans Flow 64\runtime\logs

Note that if you upgraded Flow on a previous day, the log file for that day will have been compressed and have the following filename format: flow_all_log-YYYY-MM-DD_0000.log.gz. It is important that you have the log from the date when Flow was initially upgraded.

Once you have the correct log file, look for the following phrase highlighted in red below:

12:41:33,234 [ INFO] [    1] (HibernateSchemaUpdater.java:299) - The schema version is smaller than DDL version, starting to update the schema

On the line immediately below this make a note of the number at the end of the line, highlighted in red below:

12:41:33,439 [ INFO] [    1] (HibernateSchemaUpdater.java:821) - Schema was updated to version 2.212

This number indicates the first schema update that was applied to your Flow database. In this example the database was updated schema version 212 first, so we will apply schema update 212 onwards.

Method 2
If you are installing the update in a test environment first, you can run the following SQL query on the production Flow database (assuming it has not yet been upgraded):

select *
from [flow_configuration]

Alternatively you can restore a backup of the Flow database created before Flow was upgraded, then run the above SQL query on the backup database.

The query above will return results like so:

oid	schema_version	data_version	major_version
1	211	            211	            2

Make a note of the schema_version and data_version (highlighted in red above) - these are typically the same. In this example the version is 211, so we will need to apply schema update 212 upwards.

Step 2 - Re-apply the database schema updates

The SQL scripts used to update Flow's database can be found in this folder on the server (note that you may have installed Flow on a different drive other than the C:\ drive):
C:\Program Files\Donnelley\MultiTrans Flow 64\JBoss - EWS\share\apache-tomcat-9.0.43\webapps\ROOT\WEB-INF\classes\resources\db-scripts\incremental

In this folder are two types of SQL scripts ('xxx' represents the version number):

• schema-update-xxx.sql: These 'update' scripts alter the structure of the database
• schema-populate-xxx.sql: These 'populate' scripts insert required data into the database

When updating the Flow database, the 'update' scripts are executed first followed by the 'populate' scripts.

In the example given in previous step above, we determined that schema update 212 is the next one that should be run. Copy the 'update' and 'populate' scripts from the db-scripts\incremental folder (full path shown above) numbered 212 and upwards.

Once you have all the SQL scripts, you can then apply the updates by doing the following:

1. Stop the MultiTrans Flow service on the server.
2. Manually run the schema 'update' SQL scripts in numerical order on the Flow database. E.g: schema-update-212.sql, schema-update-213.sql, etc.
3. Manually run the schema 'populate' SQL scripts in numerical order on the Flow database. E.g: schema-populate-212.sql, schema-populate-213.sql, etc.
4. Start the MultiTrans Flow service on the server.