Primavera Job Services Publication Arbiter Stops Running When Deployed in Timezone Observing Daylight Savings and Clock Moves Forward 1 Hour in Spring (Example, From GMT to BST)
(Doc ID 3022746.1)
Last updated on JULY 26, 2024
Applies to:
Primavera P6 Enterprise Project Portfolio Management - Version 17.12.0.0 to 21.12.19.0 [Release 17.12 to 21.12]Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 24.1 to 24.5 [Release 24.1 to 24.5]
Information in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
When job services is deployed to a timezone which observes Daylight Savings Time, the Project Arbiter job (responsible for queuing project publication jobs) stops running on the day/hour of the timezone transition to Daylight Savings. For example (using "London/Europe"):
- The timezone can transition between GMT to BST (Example: 31Mar24).
- The transition occurs at 1 AM, which becomes 2 AM BST.
When the job runs between the 1-2 AM hour (1-2 AM GMT = 2-3 AM BST on 31Mar24), the job's update_date reflects a time between 1-2 AM (which would reflect GMT), and stops running.
EXPECTED BEHAVIOR
The Arbiter should run as expected, even when the clock changes from Standard Time to Daylight Savings Time.
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! |