My Oracle Support Banner

E1: ORCH: Orchestrator Monitor Shows Correct Launch Information the First Time Run, Then is Off by 1 Hour with Subsequent Runs. (Doc ID 2848278.1)

Last updated on MARCH 17, 2022

Applies to:

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

Symptoms

Using SQL Server 2016, Orchestrator monitor shows correct launch information the first time run, then is off by 1 hour with subsequent runs.  

       Steps to Duplicate

  1. Create simple Orchestration to run manually to run a report
  2. Run the Orchestration and note the time stamp
  3. Go into E1 and P980060X or P980060 > Performance and see that the date/time stamp is correct.
  4. Wait a few minutes and with the same user ID, run the same Orchestration
  5. Check the table and see the second run is off by 1 hour.

                         e.g., first run shows as 9:45am, second run shows as 8:45am

 Verified all users timezone and DST setup correct and WLS includes the following argument

Customer is using MS SQL 2016. When testing with Oracle DB the issue is not found. Refer to Bug 29761357 - UTIME COLUMN IN UPDATETABLE SETS INVALID TIME - DST

Changes

 none

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


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