Ksesethighpri: (Ksb.C:3539) Failed to Elevate VKTM's Priority Found In Trace Files (Doc ID 822635.1)

Last updated on DECEMBER 06, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.1.0.7 [Release 11.1]
HP-UX PA-RISC (64-bit)
HP-UX Itanium
HP-UX PA-RISC (32-bit)
***Checked for relevance on 29-Aug-2016***

Symptoms

After applying <patch 8217795> there are many traces generated containing:

ksesethighpri: (ksb.c:3539) Failed to elevate VKTM's priority from -153 to
-179
Error Info: Category(-2), Opname(sched_setscheduler), Loc(sp.c:1755),
ErrMsg(Not owner) Dism(-10510)
*** SESSION ID:(333.1) 2009-02-20 09:43:21.906
*** SERVICE NAME:() 2009-02-20 09:43:21.906

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

*** 2009-02-20 09:43:21.906
[Start] kstmrmtickcnt = 0, ksudbrmseccnt[0] = 1235119401

--------------------------------

*** MODULE NAME:() 2009-02-20 09:43:32.536
*** ACTION NAME:() 2009-02-20 09:43:32.536

kgsksysstop: from KGSKWT_INTSTATECHNG8 retry TRUE mode
kgsksysstop: Succeeded

-------------------------

*** 2009-02-20 09:43:19.802

kewmnfy_1: gid=0, mxrwm=3, tsize=2768
kewmtotalchbsize_1(gid=0): mxent=997,maxbuc=3,total_1=0
GetCHBSize: gid=0, dtype=0, mxbuc=3, mxrwm=2, mxent=997, size=23928,
kewmtotalchbsize_2(gid=0): (0, 23928)
GetCHBSize: gid=0, dtype=1, mxbuc=3, mxrwm=1, mxent=997, size=23928,
kewmtotalchbsize_2(gid=0): (1, 47856)
kewmtotalchbsize_3(gid=0): ESQBufsize=0, Total=47856
kewmtotalchbsize_4(gid=0): TBufsize=12, Final_total=47880
kewmnfy_2: gid=0, tsize=50648
kewmnfy_3: gid=0, mxrwm=3, RRMSize=16, tsize=50696
kewmnfy_4: gid=0, mxdrm=3, DRMSize=16, tsize=50744
kewmnfy_5: gid=0, mxTMStat=0, TMsiz=4, tsize=50744

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