Okey doke!
But what about Oracle Database adjustment? Good news: Nothing to do! 😀

In Oracle words: “The Oracle RDBMS needs no patches and has no problem with the leap second changes on OS level.”

But, attention!
If your application uses timestamp or sysdate, verify the adjust of the OS Level. If it consists on a “60” second, it can result on “ORA-01852 seen 60 seconds is a illegal value for the date or timestamp dataype.”
(Insert leap seconds into a timestamp column fails with ORA-01852 (Doc ID 1553906.1))

Another possibilities is documented on these notes:NTP leap second event causing Oracle Clusterware node reboot (Doc ID 759143.1)
(Oracle VM and RHEL 4.4 to 6.2): Leap Second Hang – CPU Can Be Seen at 100% (Doc ID 1472421.1)
(OEM on Linux): Enterprise Manager Management Agent or OMS CPU Use Is Excessive near Leap Second Additions on Linux (Doc ID 1472651.1)

So, pay attention! 🙂

Here other Oracle notes that I recommend to take a look:Leap seconds (extra second in a year) and impact on the Oracle database. (Doc ID 730795.1)Leap Second Time Adjustment (e.g. on June 30, 2015 at 23:59:59 UTC) and Its Impact on Exadata Database Machine (Doc ID 1986986.1)How Leap Second Affects The OS Clock on Linux and Oracle VM (Doc ID 1453523.1)NOTE:1461363.1 – What Leap Second Affects Occur In Tuxedo?NOTE:1553906.1 – Insert leap seconds into a timestamp column fails with ORA-01852NOTE:412160.1 – Updated DST Transitions and New Time Zones in Oracle RDBMS and OJVM Time Zone File PatchesNOTE:1453523.1 – How Leap Second Affects The OS Clock on Linux and Oracle VMNOTE:1019692.1 – Leap Second Handling in Solaris – NTPv3 and NTPv4NOTE:1444354.1 – Strftime(3c) Does Not Show The Leap Second As 23:59:60NOTE:1461606.1 – Any Effect of Leap Seconds to MessageQ?