E1: SCHED: Unable to Run Scheduled Job Due to Corrupt SQLPKG
(Doc ID 1275768.1)
Last updated on DECEMBER 28, 2022
Applies to:
JD Edwards EnterpriseOne Tools - Version S23 and laterInformation in this document applies to any platform.
*** check for relevance 30-AUG-2011 ***
Symptoms
You are unable to run scheduled jobs on your Xe iSeries V5R4 Enterprise Server. Scheduler Kernel starts normally but jobs are not getting launched. Logs from the Scheduler kernel indicate that indexes are not being fetched correctly:
Scheduler kernel log contains:
Dec 21 12:41:12 ** Attempting to determine if the Scheduler is already up on this host.
Dec 21 12:41:12 ** The table, F91300, not found in table list. Returning NULL.
Dec 21 12:41:12 ** The table, F91300, with index 1, with a select array, and with the data source, DEFAULT, is not open yet. Will open it and add it to the table list.
Dec 21 12:41:12 ** Entering JDB_OpenTable( Table = F91300)
Dec 21 12:41:12 ** Entering JDB_FetchKeyed
Dec 21 12:43:32 ** Could not fetch the job header for the job, 0. Cannot launch this job.
Dec 21 12:43:32 ** Could not fetch the job header for the job, 0. Cannot launch this job
Dec 21 12:43:32 ** Could not fetch the job header for the job, 0. Cannot launch this job
Changes
Issue surfaced after rolling back an unsuccessful package deployment.
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 |