SQL Performance (MOSC)

MOSC Banner

dba_autotask_job_history and 'WINDOWS' for auto optimizer stats collection

edited Aug 19, 2015 11:20AM in SQL Performance (MOSC) 8 commentsAnswered ✓

Oracle RDBMS 12.1.0.2

SATURDAY_WINDOW starts on Saturdays at 6AM for a duration of 16 hours.

The only autotask enabled is 'auto optimizer stats collection'.

A review of dba_autotask_job_history shows that this autotask ran 4 times during the window:  6:00 AM, 10:07 AM, 2:07 PM, 6:08 PM.   The duration for 6AM was a little over 7 minutes, the others less than a minute.

Does anyone know why this runs 4 times during the window, and what else would be running during the 16-hour duration allowed?

My reason for asking is for understanding.  While my weekend stats have a job_status of SUCCEEDED, I've also defined an early AM and early PM window.  In the case of the AM window, I don't see it kicking in.  In the case of the PM window, it sometimes times out.    I'm adjusting and monitoring in development, and plan to move the methodology up the stack once I get a flow, understanding that the percentage of change is key.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center