DB2 10.5 for Linux, UNIX, and Windows
DB2 10.5 for Linux, UNIX, and Windows
This parameter specifies the maximum time difference that is permitted between members in a DB2® pureScale® environment that are listed in the node configuration file.
Each member has its own system clock. The time difference between two or more member system clocks is checked periodically. If the time difference between the system clocks is more than the amount specified by the max_time_diff parameter, warnings are logged in the db2diag log files.
In a DB2 pureScale environment, to ensure that members do not drift out of sync with each other, a Network Time Protocol (NTP) setup is required and periodically verified on each member. If the NTP daemon is not detected, warnings are logged in the db2diag log files.
The SQL1473N error message is returned in partitioned database environments where the system clock is compared to the virtual time stamp (VTS) saved in the SQLOGCTL.LFH log control file. If the time stamp in the .LFH log control file is less than the system time, the time in the database log is set to the VTS until the system clock matches the VTS.
DB2 database manager uses Coordinated Universal Time (UTC), so different time zones are not a consideration when you set the max_time_diff parameter. UTC is the same as Greenwich Mean Time.