We use CURRENT_TIMESTAMP(4) to ask the DB for it's system time.
Apparently, at least with DB2, this might return a value that is off by a multiple of one hour (3600 * 1000ms) depending on whether the OAK instance and the DB run in different timezones.
Known to work: both on the same machine.
Known to fail: OAK in CET, DB2 in UTC, in which case we're getting a timestamp one hour in the past.
At this time it's not clear whether the same problem occurs for other databases.