NTP leap second event causing Oracle Clusterware node reboot
Last updated on NOVEMBER 28, 2016
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 184.108.40.206 [Release 10.1 to 12.1]
UTC time (Coordinated Universal Time) is regularly adjusted by introducing a leap second based on the accumulated difference between the atomic clock time (TAI) and UT1, the time reflecting the Earth's rotational speed.
The decision to introduce a leap second in UTC is the responsibility of the Earth Orientation Center of the International Earth Rotation and reference System Service (IERS).
Due to the backwards time setting, NTP daemons have to adjust the time in accordance to the leap second requirement, which may affect certain versions of Oracle Clusterware to the degree that unforeseen node reboots may occur.
Leap second adjustments may affect any cluster configuration that depends on time accuracy on a per node or cluster basis, typically established by using NTP for time synchronization.
Oracle Clusterware supports two different deployments; one in which Oracle Clusterware is used as a standalone cluster solution on the system and another one in which Oracle Clusterware is used in combination with a certified third party cluster solution.
If Oracle Clusterware is used in combination with a certified third party cluster solution on your system, this note does not apply to you, as the certified third party cluster solution will handle the necessary leap second adjustments.
You should consult with your third party cluster solution provider to verify whether your cluster solution is affected by automatic leap second adjustments. For Oracle Solaris Cluster, leap second adjustments are handled automatically.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms