Effects of Leap Second On SDM (SPR and HLR) Servers

Asset ID:	1-72-2209210.1
Update Date:	2016-11-30
Keywords:

Solution Type Problem Resolution Sure

Solution 2209210.1 : Effects of Leap Second On SDM (SPR and HLR) Servers

Applies to:

Oracle Communications Subscriber Data Management (SDM) - Version SDM 9.0 and later
Tekelec

Symptoms

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.

Oracle SDM Sustaining Engineering has completed testing and confirms that no customer impact is expected at time of insertion.

Customers may experience Server High CPU alarms however they will clear within short amount of time. This will not impact to subscriber provisioning or Sh Traffic.

Cause

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).

A leap second will again be inserted at the end of December 31, 2016 at 23:59:60 UTC.

Solution

Monitor alarms and contact Oracle Support should you experience alarms that do not clear or you observe impact to subscriber provisioning or Sh Traffic.

Attachments

This solution has no attachment