E1: SCHED: After Enabling the Virtual Batch Queue Feature on Two Enterprise Servers, the Status of the Scheduled Jobs Submitted Through One Enterprise Server Were Left as "Launched"
(Doc ID 3037767.1)
Last updated on JULY 29, 2024
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
After enabling the Virtual Batch Queue feature on two enterprise servers, the status of the scheduled jobs submitted through one enterprise server were left as "Launched" as noted below:
In case the Scheduler Kernel debug logging is enabled it is observed that the submitted scheduled job is attempted to be fetched from the wrong Server Map and with the wrong execution host (not a Virtual Batch Host):
Changes
Virtual Batch Queues feature has been implemented based on the information provided in Doc ID 2748939.1 - Virtual Batch Queues (VBQ) in E1 9.2.5.x And Later - What Are They, And How Does One Set Them Up?
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 |