Time drift detected

在solaris10上安装了oracle 11.2.0.3的数据库,手工建库以后,发现告警日志里面有个非常有规律的报警信息,每隔76分钟报一次,报警信息如下:

Tue Aug 0503:05:18 2014
Time drift
detected. Please check VKTM trace file for more details.
Tue Aug 05
03:08:48 2014
Starting
background process SMCO
Tue Aug 05
03:08:48 2014
SMCO
started with pid=24, OS id=2446
Tue Aug 05
03:14:35 2014
Stopping
background process CJQ0
Tue Aug 0504:12:34 2014
Time drift
detected. Please check VKTM trace file for more details.
Tue Aug 0505:28:47 2014
Time drift
detected. Please check VKTM trace file for more details.
Tue Aug 0506:44:59 2014
Time drift
detected. Please check VKTM trace file for more details.
Tue Aug 0508:01:26 2014
Time drift
detected. Please check VKTM trace file for more details.
Tue Aug 05
09:17:33 2014
Time drift
detected. Please check VKTM trace file for more details.

告警日志提示看trace文件,trace文件内容如下:

[[email protected]:/u01/app/oracle/diag/rdbms/anny/anny/trace]$
cat anny_vktm_2378.trc
Trace file
/u01/app/oracle/diag/rdbms/anny/anny/trace/anny_vktm_2378.trc
Oracle
Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the
Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME
= /u01/app/oracle/product/11.2.0/dbhome_1
System
name:    SunOS
Node
name:      solaris186
Release:        5.10
Version:        Generic_142910-17
Machine:        i86pc
Instance
name: anny
Redo
thread mounted by this instance: 0 <none>
Oracle
process number: 4
Unix
process pid: 2378, image: [email protected] (VKTM)
 
 
***
2014-08-05 02:58:43.036
***
SESSION ID:(4.1) 2014-08-05 02:58:43.036
*** CLIENT
ID:() 2014-08-05 02:58:43.036
***
SERVICE NAME:() 2014-08-05 02:58:43.036
*** MODULE
NAME:() 2014-08-05 02:58:43.036
*** ACTION
NAME:() 2014-08-05 02:58:43.036
 
kstmmainvktm:
succeeded in setting elevated priority
highres_enabled
 
***
2014-08-05 02:58:43.036
VKTM
running at (10)millisec precision with DBRM quantum (100)ms
[Start]
HighResTick = 59404806322
kstmrmtickcnt
= 0 : ksudbrmseccnt[0] = 1407178723
 
***
2014-08-05 03:05:18.798
kstmchkdrift
(kstmhighrestimecntkeeper:highres): Time jumped forward by (1297157)usec at
(59800568177) whereas (1000000) is allowed
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Time stalled at 1407180887
 
***
2014-08-05 03:34:48.908
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Stall, backward drift ended at 1407180888
drift: 1
 
***
2014-08-05 03:35:18.823
kstmchkdrift
(kstmhighrestimecntkeeper:highres): Time jumped forward by (1366639)usec at
(61602594030) whereas (1000000) is allowed
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Time stalled at 1407183154
 
***
2014-08-05 04:12:35.900
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Stall, backward drift ended at 1407183155
drift: 1
 
***
2014-08-05 04:12:51.999
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Time stalled at 1407183171
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Stall, backward drift ended at 1407183172
drift: 1
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Time stalled at 1407185440
 
***
2014-08-05 04:50:41.947
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Stall, backward drift ended at 1407185441
drift: 1
 
***
2014-08-05 04:50:58.972
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Time stalled at 1407185458
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Stall, backward drift ended at 1407185459
drift: 1
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Time stalled at 1407187727
 
***
2014-08-05 05:28:48.883
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Stall, backward drift ended at 1407187728
drift: 1
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Time stalled at 1407187744
 
***
2014-08-05 05:29:05.931
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Stall, backward drift ended at 1407187745
drift: 1
 
***
2014-08-05 05:43:59.944
kstmchkdrift
(kstmhighrestimecntkeeper:highres): Time jumped forward by (1252499)usec at
(69329714522) whereas (1000000) is allowed
kstmchkdrift
(kstmhighrestimecntkeeper:highres): Time jumped forward by (1419573)usec at
(70537192617) whereas (1000000) is allowed
 
***
2014-08-05 06:06:53.993
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Time stalled at 1407190013
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Stall, backward drift ended at 1407190014
drift: 1
 
***
2014-08-05 06:07:11.988
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Time stalled at 1407190031
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Stall, backward drift ended at 1407190032
drift: 1
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Time stalled at 1407192299
 
***
2014-08-05 06:45:00.927
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Stall, backward drift ended at 1407192300
drift: 1
 
***
2014-08-05 06:45:17.960
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Time stalled at 1407192317
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Stall, backward drift ended at 1407192318
drift: 1
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Time stalled at 1407194588
 
***
2014-08-05 07:23:09.922
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Stall, backward drift ended at 1407194589
drift: 1
 
***
2014-08-05 07:23:26.979
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Time stalled at 1407194606
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Stall, backward drift ended at 1407194607
drift: 1
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Time stalled at 1407196886
 
***
2014-08-05 08:01:27.919
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Stall, backward drift ended at 1407196887
drift: 1
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Time stalled at 1407199171
 
***
2014-08-05 08:39:32.932
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Stall, backward drift ended at 1407199172
drift: 1
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Time stalled at 1407201453
 
***
2014-08-05 09:17:34.920
kstmchkdrift
(kstmhighrestimecntkeeper:lowres): Stall, backward drift ended at 1407201454
drift: 1

从trace文件没有得到有用的信息,但这个信息不影响数据库的使用,查看官方文档说这是一个bug,网上说是因为vktm这个进程每隔一段时间会与ntp server进行对时,但我机器的ntp 服务是没有打开的。

[[email protected]:/]#
svcs -a ntp  
svcs: -a
ignored when used with arguments.
STATE          STIME    FMRI
disabled       10:30:01 svc:/network/ntp:default

在Oracle Database
11g中,VKTM是一个新增的后台进程。这个进程的含义是:

VKTM (virtual keeper
of time) is responsible for providing a wall-clock time (updated every second)
and reference-time counter (updated every 20 ms and available only when running
at elevated priority).

也就是说,这个进程用于提供一个数据库的时钟,每秒更新;或者作为参考时间计数器,这种方式每20毫秒更新一次,仅在高优先级时可用。

通过VKTM进程,数据库可以降低和操作系统的交互,Kamus的解释是:在11g之前所有的Oracle数据库后台或者前台进程如果需要获得当前时间信息,就需要调用操作系统的gettimeofday()函数或者说是相类似的函数。而VKTM进程就是专门用来获得时间信息然后将信息存放在SGA中供其它进程使用,这样其它进程当需要时间信息的时候,只要到SGA的某个内存位置去获得就好,而不用频繁调用gettimeofday()函数。毫无疑问,这样效率会更高。

在RAC测试中,Oracle
1.1.0.6版本LMSx进程获取时间信息时,可以从VKTM进程中获益大概70%的速度提升,而11.1.0.7将会更高。同时,因为gettimeofday()函数也引发了很多bug,所以无论是RAC还是NORAC库,都将从VKTM进程中获益。

最后结论:

猜测这个bug在所有平台上都有可能触发,由于我机器的ntp服务没有启动,所以vktm进程与ntp服务进行对时,触发了这个bug。如果你机器上有ntp 服务,那么时间差异大的话也会触发这个bug。

Time drift detected

时间: 2024-11-05 21:31:07

Time drift detected的相关文章

Google Hacking Database(2016-2017最新)

inurl:share.cgi?ssid=                                  ##云服务器文件和文件夹共享intitle:"Welcome to QNAP Turbo NAS"      ##  QNAP登录页面inurl:"img/main.cgi?next_file"                     ##在线摄像头ext:log inurl:"/pgadmin"                    

我的oracle 健康检查报告

最近一直想用sql来生成oracle的健康检查报告,这样看起来一目了然,经过网上搜资料加自己整理终于算是成型了,部分结果如下图所示, 具体参考附件,恳请广大网友看看是否还有需要添加的地方. DB_healthcheck_by_lhr_ORADG11G_20150826160539.zip ORADG11G 数据库巡检报告 Copyright (c) 2015-2100 (http://blog.itpub.net/26736162) lhrbest. All rights reserved. 巡

Oracle集群(RAC)时间同步(ntp和CTSS)

Oracle集群(RAC)时间同步(ntp和CTSS) http://blog.itpub.net/26736162/viewspace-2157130/ crsctl stat res -t -init ps -ef|grep ctss crsctl check ctss cluvfy comp clocksync -n all -verbose crsctl start res ora.ctssd -init crsctl stop res ora.ctssd -init Network T

Ceph 时钟偏移问题 clock skew detected 解决方案--- 部署内网NTP服务

告警:HEALTH_WARN clock skew detected on mon.ip-10-25-195-6; 8 requests are blocked > 32 sec; Monitor clock skew detected 原因: MON可能被MON节点之间的重要的时钟偏移激烈的影响.这经常会转变为没有明显原因的诡异的行为.为了避免这种问题,你应该在MON节点上运行一个时间同步的工具. 默认最大容忍的时钟偏移为0.05s,不建议修改这个官方开发推荐值.私自未经测试修改虽然无数据丢失

ceph集群报 Monitor clock skew detected 错误问题排查,解决

ceph集群报 Monitor clock skew detected 错误问题排查,解决           告警信息如下: [[email protected] ceph]# ceph -w    cluster ddc1b10b-6d1a-4ef9-8a01-d561512f3c1d     health HEALTH_WARN            clock skew detected on mon.ceph-100-81, mon.ceph-100-82            Mon

Terraform Detecting Drift

转自:https://www.terraform.io/docs/extend/best-practices/detecting-drift.html 这篇文章主要说明了对于资源如何处理 read&&create,可以让我们了解如何进行状态管理 One of the core challenges of infrastructure as code is keeping an up-to-date record of all deployed infrastructure and thei

C语言错误: CRT detected that the application wrote to memory after end of heap buffer

CRT detected that the application wrote to memory after end of heap buffer 多是中间对其进行了一些操作,在程序结束处,释放内存的时候,引起错误: HEAP CORRUPTION DETECTED:after Normal block(#***) at 0x****.CRT detected that application wrote memory after end of heap buffer. 错误原因: 以对内在操

ubuntu 14.04 ns2.35 ***buffer overflow detected **: ns terminated解决办法

1.按照如下教程安装 Install With Me !: How to Install NS-2.35 in Ubuntu-13.10 / 14.04 (in 4 easy steps) 2.运行一个例子程序时出现 ***buffer overflow detected **: ns terminated 3.参考现有方案出现,gcc error:4.4没有那个文件或目录 sudo apt-get intall gcc-4.4 sudo apt-get intall g++-4.4 修改tcl

解决:Detected memory leaks

最近在一个项目中,程序退出后都出现内存泄漏: Detected memory leaks!Dumping objects ->{171} normal block at 0x05785AD0, 12 bytes long.Data: << N       N x 7 > 3C AC 4E 10 00 00 00 00 BC A4 4E 10 78 B6 37 00Object dump complete. 解决方法: 1.在程序中的尽可能靠近启动代码的地方(足够前的地方,只要在泄漏