Start at unintended time after changing maintenance job start and run times
(Doc ID 2907968.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 19.3.0.0.0 and laterOracle Database - Standard Edition - Version 19.3.0.0.0 and later
Information in this document applies to any platform.
Symptoms
Even the Window start time and duration have been changed, the jobs are still running at unintended time.
For example, reviewing the definition of TUESDAY_WINDOW as follows:
The job start time supposed to be 8:00, but auto optimizer stats collection and auto space advisor run twice at 8:00 and 12:00.
Changes
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 |