The Database Server Is Creating A Lot Of Trace Files From the VKTM Process (Doc ID 837105.1)

Last updated on DECEMBER 06, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.7 to 11.2.0.2 [Release 11.1 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 02-Jul-2016***



Symptoms

You are receiving several trace files from the VKTM process.

The traces vktm_xxxx.trc are similar to:


System name: Linux
Node name: <your node name>
Release: <your kernel version>
Version: #1 SMP Thu May 7 18:02:47 EDT 2009
Machine: <architecture>
Instance name: <instance name>
Redo thread mounted by this instance: 0 <none>
Oracle process number: 3
Unix process pid: 9419, image: <oracle@node name> (VKTM)


*** 2009-05-22 11:01:35.340
*** CLIENT ID:() 2009-05-22 11:01:35.340
*** SERVICE NAME:() 2009-05-22 11:01:35.340
*** MODULE NAME:() 2009-05-22 11:01:35.340
*** ACTION NAME:() 2009-05-22 11:01:35.340

ksesethighpri: (ksb.c:3539) Failed to elevate VKTM's priority from 0 to 1
Error Info: Category(-2), Opname(skgdism_create), Loc(sp.c:1529), ErrMsg(Error 0) Dism(-1081305598)
*** SESSION ID:(333.1) 2009-05-22 11:01:35.342
*** SERVICE NAME:() 2009-05-22 11:01:35.342

kstmmainvktm: failed in setting elevated priority
kstmmainvktm:enabled, highres_enabled, sectick_enabled
VKTM running at (100ms) precision

*** 2009-05-22 11:01:35.342
[Start] kstmrmtickcnt = 0, ksudbrmseccnt[0] = 1243004495

*** 2009-05-22 11:07:46.374
[End] kstmrmtickcnt = 3659, ksudbrmseccnt[365] = 1243004865



When using Solaris Zone a similar set of errors can occur:
ksesethighpri: (ksb.c:3786) Failed to elevate VKTM's priority from -100 to 1
Error Info: Category(-2), Opname(skgdism_send), Loc(sp.c:1539), ErrMsg(Not owner) Dism(2147475174)
*** SESSION ID:(1135.1) 2010-01-13 15:43:58.171
*** SERVICE NAME:() 2010-01-13 15:43:58.171

kstmmainvktm: failed in setting elevated priority
Verify: SETUID is set on ORADISM and restart the instance
kstmmainvktm:enabled, highres_enabled, sectick_enabled
VKTM running at (100ms) precision
Parameter _dbrm_quantum will not be effective

Changes

Applying <Patch:8217795> has been know to cause this problem. Other OS changes may trigger this as well. 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms