How Leap Second Impacts OCUDR.

Asset ID:	1-77-2203373.1
Update Date:	2016-11-15
Keywords:

Solution Type Sun Alert Sure

Solution 2203373.1 : How Leap Second Impacts OCUDR.

Applies to:

Oracle Communications User Data Repository - Version UDR 10.0 to UDR 12.1 [Release UDR 10.0 to UDR 12.0]
Tekelec

Description

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. 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. The purpose of a leap second is to compensate for this drift, by scheduling days with 86401 or 86399 seconds. Insertion of each UTC leap second is usually decided about six months in advance by the International Earth Rotation and Reference Systems Service (IERS).

Occurrence

A leap second will again be inserted at the end of December 31, 2016 at 23:59:60 UTC. This event can cause application and OS level malfunctions on systems with vulnerable operating systems.

Symptoms

The following OCUDR releases ARE impacted by this event: 10.0 and 10.0.1

The following OCUDR releases ARE NOT impacted by this event: 10.2 and 12.1

Customers running UDR 10.0 or 10.0.1 will observe the following on their systems when leap second is introduced.

Active NOAMP will display all or a few of these minor alarms below on the GUI

31119: DB Update log Overrun
31100 : DB Replication Fault
31101 : DB Replication to Slave Failure

Alarms will auto clear after 5 minutes.
There will be no Provisioning or signaling traffic failures during this period.

History

14-NOV-2016

Attachments

This solution has no attachment