My Oracle Support Banner

Scheduled jobs do not run as expected after 10.2 upgrades (Doc ID 731678.1)

Last updated on JANUARY 30, 2022

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 10.2]
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
Information in this document applies to any platform.


Scheduled jobs are not automatically run at the expected time frames after a database upgrade.

Possible symptoms include but are not limited to the following:
The scheduler processes use large amounts of CPU and try to stop the Scheduler, the CJQ processes refuse to halt. If you try to kill -9 the CJQ processes, they just respawn. The Scheduler appears to hang

You may also see trace files with the following messages:

jsksGetCurWindowId:1 got error 27468
jsksGetCurWindowId:1 got error 27468


* Recently database has been upgraded to either or or


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

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