E1: SCHED: Scheduler Kernel Fails After DST Change Due to Job in Launched Status
(Doc ID 1077437.1)
Last updated on NOVEMBER 14, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
Microsoft Windows (32-bit)
After adjusting for Daylight Savings, Scheduler stops running jobs. The Scheduler Kernel goes down and no jobs are running. You have tried to stop and start the Scheduler Kernel using P91300 but you get an error:
Please contact your system Administrator.
After stopping/starting JDE Service on the Enterprise Server the Scheduler Kernel starts but in P91300, the Scheduler server still shows it is down and no jobs are being submitted. When starting the kernel it will not start successfully. It leaves an orphaned jdenet_k job.
The Enterprise Servers are in a Microsoft Cluster. The Scheduler kernel JDE.LOG has the following:
3820/9236 MAIN_THREAD Mon Mar 15 23:59:28.408000 ipcmisc.c299
process 3820 <jdenet_k> registered in entry 1
3820/9236 MAIN_THREAD Mon Mar 15 23:59:28.424000 Netcfg.c296
Starting Kernel of Type:SCHEDULER KERNEL
3820/9236 MAIN_THREAD Mon Mar 15 23:59:29.424001 sc_dsptc.c144
INITIALIZING SCHEDULER SERVER KERNEL
3820/9236 MAIN_THREAD Mon Mar 15 23:59:29.424002 sc_dsptc.c167
Attempting to auto-start the Scheduler.
3820/9236 MAIN_THREAD Mon Mar 15 23:59:34.674000 Jdb_cach.c920
JDB3800033 - Warning... Table F99410 is already cached.
3820/9236 MAIN_THREAD Mon Mar 15 23:59:35.283000 sc_dsptc.c981
Auto-starting the Scheduler Server
The OCM mappings for F91300, F91310 and F91320 have been checked for the Enterprise Server and they all look fine. The Cluster Name can be pinged and note that the IP address is the same as the one referred to in the logs.
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