Scenario: Changing the system clock
When adjusting or changing the system clock, there is no reason to stop the
Db2® database
manager. Db2 successfully handles daylight saving time changes twice a year all over the world
without issue.
Configurations which use NTP to synchronize clocks across systems are
also fully supported.
About this task
There are some best practices that you must be aware of when changing the system time.
Restrictions
When changing the system clock in the vast majority of scenarios there is absolutely no impact.
When major time shifts occur, you must be aware of two situations.
- If you execute point-in-time recovery you need to be aware of any significant time shifts.
- Function definitions include the time and date they were created in the form of a timestamp. At function invocation, Db2 attempts to resolve the function definition. As part of the function resolution, the timestamp value logged in the function definition at create time is checked. If you move the system clock back to a time before the functions were created, Db2 does not resolve references to those functions.
Procedure
Best practices to avoid these two situations:
Results
By following the best practices as outlined, you avoid any potential point-in-time recovery or function resolution issue when changing the system clock.