In Oracle Analytics Publisher, Individual Job History Not Visible After Frequency Change on Existing Schedule
(Doc ID 3036776.1)
Last updated on JULY 26, 2024
Applies to:
Oracle Analytics Cloud - Version N/A and laterInformation in this document applies to any platform.
Symptoms
Individual Job History is not visible after updating the job schedule.
Following are the steps to reproduce the issue:
- Create a job to run with a frequency of 5 minutes.
- Once it runs few times, Update the same job and change the frequency (For example, 10 minutes) and click on Submit (and not submit as new).
- Manage Jobs will show the history prior to update and will not reflect the history after the same job is updated. The job ID changes even though it was not submitted as New.
- Updating the same job sometimes does not reflect the change.
- For example, if the frequency is changed from 1 min to 6 hrs, the job was still running every 1 min possibly because the update created a new job id, instead of changing the original job.
It is expected that clicking on submit should not be creating a new job ID.
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 |
Cause |
Solution |
References |