My Oracle Support Banner

After 11.2.0.4 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 JULY 05, 2023

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.4 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Solaris on x86-64 (64-bit)

Symptoms

Every time while the database instance is being started, the following message occurs in the alert log:

Warning: VKTM detected a time drift.
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:

ksesethighpri: (ksb.c:4201) Failed to elevate VKTM's priority from -100 to 60
Error Info: Category(-2), Opname(skgdism_send), Loc(sp.c:1667), ErrMsg(Not
owner) Dism(1024)
kstmmainvktm: failed in setting elevated priority
Verify: SETUID is set on ORADISM and restart the instance
highres_enabled
VKTM running at (100ms) precision
kstmrmtickcntkeeper: param _dbrm_quantum will not be effective

 

Changes

 The following was already checked:

1- ORADISM has expected permissions as per Note 1562142.1

2- Patch 11837095 is installed (as BUG 11837095 is fixed on 11.2.0.4)

3- Event 10795 is set

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.