After 22.214.171.124 upgrade, getting traces with Ksesethighpri: (ksb.c:4201) Failed To Elevate VKTM's Priority From -100 To 60
(Doc ID 1926661.1)
Last updated on FEBRUARY 20, 2019
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Solaris on x86-64 (64-bit)
***Checked for relevance on 13-Sep-2016***
Every time while the database instance is being started, the following message occurs in the alert log:
Time drifts can result in an unexpected behavior such as time-outs. Please
check trace file for more details.
The generated trace files includes the following information:
Error Info: Category(-2), Opname(skgdism_send), Loc(sp.c:1667), ErrMsg(Not
kstmmainvktm: failed in setting elevated priority
Verify: SETUID is set on ORADISM and restart the instance
VKTM running at (100ms) precision
kstmrmtickcntkeeper: param _dbrm_quantum will not be effective
The following was already checked:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document