My Oracle Support Banner

E1: SCHED: Troubleshooting Job Launch Related Issues And Scheduler Service issues for EnterpriseOne Scheduler (P91300) (Doc ID 1353038.1)

Last updated on MARCH 20, 2024

Applies to:

JD Edwards EnterpriseOne Tools - Version SP24 and later
Information in this document applies to any platform.


This document provides known issues and solutions for basic troubleshooting of EnterpriseOne Scheduler Job Launch issues and includes details on gathering information for logging a Service Request with Oracle Support.

Troubleshooting Steps

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
Troubleshooting Steps
 Basic Troubleshooting Guide for Scheduler Job Launch issues
 Symptom 1:  Scheduled jobs do not launch /cannot start Scheduler or there is delay in launch of scheduled jobs
 Symptom 2:  Job launches but an error is set in the status field
 Symptom 3:  After scheduling job no server job number is assigned and job is not submitted to AS/400 subsystem
 Symptom 4:  Scheduled batch jobs are not being submitted for execution
 Symptom 5:  Scheduler jobs run twice when submitted
 Symptom 6:  Scheduled job fails when scheduled with no END DATE defined
 Symptom 7:  Scheduler Server job status not being updated with Oracle database
 Symptom 8:  Jobs launched from Scheduler process are different than those launched from Batch Versions
 Symptom 9:  Failed to notify the Scheduler Kernel of a control record change
 Symptom 10:  Scheduler comes to a standstill and gives message: JDB9900376 - Failed to initialize EXCL_APP_SEC Cache
 Symptom 11:  Some scheduled jobs do not get a server Job Number
 Symptom 12:  Scheduled jobs with OSA Setup is ignored
 Symptom 13:  New scheduler jobs fail to run
 Symptom 14: Starting scheduler kernel throws error in the logs and causes scheduler to fail
 Symptom 15: JDE Scheduler not starting after service restart
 Symptom 16: Scheduler crashes everyday morning at a specific time.
 Symptom 17: While scheduling jobs, the passwords are not stored correctly. They are displayed with one character only.
 Symptom 18: The Scheduled Jobs are not submitted and when trying to stop the scheduler server from P91300 application error is displayed on screen.
 Symptom 19: Scheduler Server shows incorrect status in P91300 and Scheduler hangs after some time
 Symptom 20: Scheduled jobs are getting deleted randomly. The related data or records is getting deleted from F91320 as well.
 Symptom 21:  Issue with jobs submitted via Skybot scheduler
 Symptom 22: Expected Scheduler Kernel fixes not working after update package for Scheduler Kernel objects
 Symptom 23: Recurring scheduler jobs are no longer running and new scheduler jobs are not saved
 Symptom 24: One specific version of a standard UBE which is scheduled on AS400 scheduler gets stuck frequently
 Further Diagnosing Scheduler Problems

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