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

Last updated on DECEMBER 06, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.3 to 10.2.0.5 [Release 10.2]
Information in this document applies to any platform.
***Checked for relevance on 02-Sep-2016***

Symptoms

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



Changes

* Recently database has been upgraded to either 10.2.0.3 or 10.2.0.4 or 10.2.0.5.

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