Problem Summary
---------------------------------------------------
Warning: VKTM detected a time drift
Problem Description
---------------------------------------------------
We found below problem from dc and dr alert log file .
Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more det.
Please assist us on above warning . Will it impact on business?
Solution :
The time drifts usually occurring less than 1sec and 5 sec for forward and backward respectively are permissible and OK.
If the traces are emitting time drifts of amount beyond these ranges, then it needs to be analyzed.
Most of the times, during high loads, there would be issues with underlying OS due to virtual memory, network time protocol improper configuration etc.
In general VKTM process need to be scheduled in every 10ms, if due to above reasons this is not happening we see the time drifts and to certain level (mentioned above) are permissible.
So please upload the VKTM trace files to analyze.
You can also set the below event to supress these alerts in alert log:
==========================================
Event 10795 is not set in the database.
Event 10795 suppress the VKTM warnings in alert log file. Hence the event need to be set.
$ sqlplus / as sysdba
alter system set events '10795 trace name context forever, level 2' scope=spfile;
shut immediate
startup
oradebug setmypid
oradebug eventdump system
The last command should show you the 10795 event set in your system.
---------------------------------------------------
Warning: VKTM detected a time drift
Problem Description
---------------------------------------------------
We found below problem from dc and dr alert log file .
Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more det.
Please assist us on above warning . Will it impact on business?
Solution :
The time drifts usually occurring less than 1sec and 5 sec for forward and backward respectively are permissible and OK.
If the traces are emitting time drifts of amount beyond these ranges, then it needs to be analyzed.
Most of the times, during high loads, there would be issues with underlying OS due to virtual memory, network time protocol improper configuration etc.
In general VKTM process need to be scheduled in every 10ms, if due to above reasons this is not happening we see the time drifts and to certain level (mentioned above) are permissible.
So please upload the VKTM trace files to analyze.
You can also set the below event to supress these alerts in alert log:
==========================================
Event 10795 is not set in the database.
Event 10795 suppress the VKTM warnings in alert log file. Hence the event need to be set.
$ sqlplus / as sysdba
alter system set events '10795 trace name context forever, level 2' scope=spfile;
shut immediate
startup
oradebug setmypid
oradebug eventdump system
The last command should show you the 10795 event set in your system.
No comments:
Post a Comment