Schedule Frequency Has Changed Or Been Removed Without Anyone Actually Adjusting The Frequency For A Data Source Within The Analytics Administration Application
Last updated on MAY 18, 2018
Applies to:Primavera Analytics Cloud Service - Version 18.104.22.168 to 22.214.171.124 [Release 16.2]
Primavera Data Warehouse - Version 126.96.36.199 to 188.8.131.52 [Release 16.1 to 16.2]
Primavera Analytics - Version 184.108.40.206 to 220.127.116.11 [Release 16.1 to 16.2]
Information in this document applies to any platform.
After configuring a schedule frequency within the Analytics Administration Application, the frequency was reset or removed without anyone actually making a change to the frequency. This causes the scheduled intervals to stop running.
After configuring a schedule frequency, for the frequency to remain constant if no change is made.
STEPS TO DUPLICATE
1. Schedule the ETL to run a particular interval.
2. Check daily until it is found that the scheduled ETL did not run.
Note, it was found that an ETL failure is one possible situation that can trigger this situation to occur (but not limited to this situation).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms