Handling the leap second

Leap Second – What is it?

From wiki

A leap second is a one-second adjustment that is occasionally applied to Coordinated Universal Time (UTC) in order to keep its time of day close to the mean solar time, or UT1. Without such a correction, time reckoned by Earth’s rotation drifts away from atomic time because of irregularities in the Earth’s rate of rotation.

Leap Time Jun 30 2015

We will have leap second on Jun 30th this year and it means that this year the last minute of June 30th will be one second longer and “June 30, 2015 23:59:60″ will be a valid and correct time. There may be few issues caused by leap second and below is the summary of my findings

Genesys

There will be minor issues on reporting products and can be fixed by adjusting time through NTP. I suggest to synchronize time on server on 01 July 2015 01:00 hours on all Genesys Servers.

Operating System (Windows, IBM AIX and Redhat LInux)

Microsoft (http://blogs.msdn.com/b/mthree/archive/2012/07/01/leap-second-070112.aspx) and IBM (http://www-01.ibm.com/support/docview.wss?uid=isg3T1022057) confirmed that there will not be any issues.

Red hat linux is impacted by leap second and fix is available for this. More details can be found at https://access.redhat.com/articles/15145

Databases (Oracle and SQL Server)

• SQL Server – No impact as it receives time from Windows
• Oracle – Oracle notes that there may be multiple issues (System Hang, 100% CPU utilization etc) on LInux environment (https://blogs.oracle.com/oem/entry/oracle_support_note_for_leap). Refer to the above link for MOS note to fix this issue in your environment