Warning: VKTM detected a time drift in STANDBY Database on Linux 64 bit

Issue:

Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.

*** 2016-07-21 08:15:26.137
*** CLIENT ID:() 2016-07-21 08:15:26.137
*** SERVICE NAME:() 2016-07-21 08:15:26.137
*** MODULE NAME:() 2016-07-21 08:15:26.137
*** ACTION NAME:() 2016-07-21 08:15:26.137

ksesethighpri: (ksb.c:4201) Failed to elevate VKTM's priority from 0 to 1
Error Info: Category(-2), Opname(skgdism_create), Loc(sp.c:1553), ErrMsg(Error 0) Dism(16)
*** SESSION ID:(801.1) 2016-07-21 08:15:26.140
*** SERVICE NAME:() 2016-07-21 08:15:26.140
ghres_enabled
VKTM running at (100ms) precision
kstmrmtickcntkeeper: param _dbrm_quantum will not be effective

or 

*** 2016-07-20 22:40:57.760
VKTM running at (1)millisec precision with DBRM quantum (100)ms
[Start] HighResTick = 1469034657760082
kstmrmtickcnt = 0 : ksudbrmseccnt[0] = 1469034657
kstmchkdrift (kstmhighrestimecntkeeper:highres): Time jumped forward by (3530316)usec at (1469035949221501) whereas (1000000) is allowed

Solution:

The time drifts usually occurring less than 1sec and 5 sec for forward and backward respectively are permissible. Most of the times, during high loads, there would be issues with underlying OS due to virtual memory, network time protocol improper configuration etc.

The resource manager to take improper decisions and can lead to a hang in worst case.

To fix the issue, please download and apply patch 11837095 as available for your release/platform.

After applying the patch, enable event 10975 at level 2:

alter system set event="10795 trace name context forever, level 2" scope=spfile;

Then bounce the instance (shutdonw then startup) for the event to be applied.

The permanent fix is planned to be included in the 11.2.0.4 and 12.1 releases.