Leap Second has no impact on eHealth

Document created by natma01 Employee on Jan 13, 2016Last modified by SamCreek on Dec 17, 2016
Version 2Show Document
  • View in full screen mode

 

Hello, eHealth Community,

 

I want to confirm that you should not expect any problems on or around June 30, 2015 related to the "Leap Second" clock adjustment. As in 2008, and most recently 2012, no problems arose with eHealth performance or functionality with the OS clock adjustments related to the UTC time adjustment.

 

 

Details:  

There is no need for eHealth Administrators or Users to be concerned with this "Leap Second" (UTC) time adjustment. Such adjustments have become somewhat routine since 1972. In addition, no patch is required for eHealth's Oracle database, as this is an OS clock adjustment, not a db adjustment. (The Oracle DST functions are for addressing time zone differences.)  Following is an illustration of what happens to a system clock during this adjustment:

 

After 23:59:59.9, the time reverts back to 23.59.59.0 in this sequence:

 

23:59:59.7
23:59:59.8
23:59:59.9
23:59:59.0 

23:59:59.1

 

etc.

 

There should be no problem with eHealth's data time stamps related to this adjustment. 

 

A bit more info on leap second:

A leap second is added on the last day of June or the last day of December as dictated by the IERS (International Earth Rotation and Reference System Service). Ideally, all the systems in the World insert the leap second at exactly the same moment.

 

###

More Information:

 

For more info, please visit http://www.timeanddate.com/time/aboututc.html and https://hpiers.obspm.fr/iers/bul/bulc/bulletinc.49

 

-Margaret, eHealth PM

 

Thanks Margaret ! Good to be in the know.

 

This document was generated from the following discussion: Leap Second has no impact on eHealth

Attachments

    Outcomes