RE: autotask not running for a while

I did some more looking, and noticed that it ran on the weekend maintenance 
window, but now the windows are scheduled again until this Friday. Any idea 
why? Does Oracle just decide it doesn't think things change enough that it 
doesn't need to for a while, or is there something else going on?
(it ran during this weekend's window)
auto optimizer stats collection          SUCCEEDED                      
03-MAR-12 01.00.08.617889 PM UTC
auto space advisor                       SUCCEEDED                      
03-MAR-12 01.00.08.673222 PM UTC
sql tuning advisor                       SUCCEEDED                      
03-MAR-12 01.00.08.722649 PM UTC

69 rows selected.

Now, the windows aren't scheduled again til next Friday?
SQL> select * from dba_scheduler_window_groups;

WINDOW_GROUP_NAME              ENABL NUMBER_OF_WINDOWS NEXT_START_DATE
------------------------------ ----- ----------------- 
----------------------------------------------------------------
COMMENTS
--------------------------------------------------------------------------------------------------------------------------------------------
MAINTENANCE_WINDOW_GROUP       TRUE                  7 09-MAR-12 
05.00.00.000000 AM UTC
Window group for Automated Maintenance

ORA$AT_WGRP_OS                 TRUE                  7 09-MAR-12 
05.00.00.000000 AM UTC
auto optimizer stats collection

ORA$AT_WGRP_SA                 TRUE                  7 09-MAR-12 
05.00.00.000000 AM UTC
auto space advisor

ORA$AT_WGRP_SQ                 TRUE                  7 09-MAR-12 
05.00.00.000000 AM UTC
sql tuning advisor

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Walker, Jed S
Sent: Friday, March 02, 2012 10:47 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: autotask query

We have a system that runs on UTC and is active during the day in North 
America. As such I recently changed the autotask used maintenance windows so 
that they would run during the N.A. nighttime. After I did this, the next day 
the jobs ran when expected (the new time), but then didn't run for about a 
week. I was getting worried something had gotten messed up but then finally 
last night they did run as expected.
You can see what I did here 
http://tinky2jed.wordpress.com/oracle-stuff/changing-the-oracle-database-default-maintenance-window-time/

I was thinking maybe it didn't think there was any work to do, but I would 
think it still would kick off the job to figure that out. So, I'm still 
wondering why it didn't run for almost a week. Prior to that it seems it has 
run every day during the week.

Running at the default times
sql tuning advisor                       SUCCEEDED                      
19-FEB-12 06.00.02.365020 AM UTC    +000 00:07:06
auto optimizer stats collection          SUCCEEDED                      
19-FEB-12 06.00.08.132191 AM UTC    +000 03:39:37
auto space advisor                       SUCCEEDED                      
19-FEB-12 06.00.08.176655 AM UTC    +000 17:36:34
auto optimizer stats collection          SUCCEEDED                      
20-FEB-12 10.00.02.106531 PM UTC    +000 03:12:36
auto space advisor                       STOPPED                        
20-FEB-12 10.00.07.821675 PM UTC    +000 03:59:52
sql tuning advisor                       SUCCEEDED                      
20-FEB-12 10.00.07.868723 PM UTC    +000 00:21:15
auto optimizer stats collection          SUCCEEDED                      
21-FEB-12 10.00.09.031744 PM UTC    +000 03:37:24
auto space advisor                       STOPPED                        
21-FEB-12 10.00.09.041172 PM UTC    +000 03:59:51
sql tuning advisor                       SUCCEEDED                      
21-FEB-12 10.00.09.090205 PM UTC    +000 00:11:34
auto optimizer stats collection          SUCCEEDED                      
22-FEB-12 10.00.07.951870 PM UTC    +000 03:31:40
auto space advisor                       STOPPED                        
22-FEB-12 10.00.07.971702 PM UTC    +000 03:59:52
sql tuning advisor                       SUCCEEDED                      
22-FEB-12 10.00.08.004047 PM UTC    +000 00:02:00
Changed the window time, and runs at new times
auto optimizer stats collection          SUCCEEDED                      
24-FEB-12 05.00.02.586962 AM UTC    +000 03:23:57
auto space advisor                       STOPPED                        
24-FEB-12 05.00.07.957369 AM UTC    +000 03:59:52
sql tuning advisor                       SUCCEEDED                      
24-FEB-12 05.00.07.968124 AM UTC    +000 00:01:58
auto space advisor                       SUCCEEDED                      
25-FEB-12 01.00.02.499372 PM UTC    +000 12:33:12
auto optimizer stats collection          SUCCEEDED                      
25-FEB-12 01.00.09.406688 PM UTC    +000 03:59:18
sql tuning advisor                       SUCCEEDED                      
25-FEB-12 01.00.09.413130 PM UTC    +000 00:12:37
Doesn't run for almost a week, then finally does at correct "new" time
sql tuning advisor                       SUCCEEDED                      
02-MAR-12 05.00.02.579958 AM UTC    +000 00:26:42
auto optimizer stats collection          STOPPED                        
02-MAR-12 05.00.08.646075 AM UTC    +000 03:59:53
auto space advisor                       STOPPED                        
02-MAR-12 05.00.08.689854 AM UTC    +000 03:59:53


- Jed


--
http://www.freelists.org/webpage/oracle-l




--
http://www.freelists.org/webpage/oracle-l


Other related posts:

  • » RE: autotask not running for a while - Walker, Jed S