statistics – Oracle gather stats autotask being interrupted before maintenance window ends

a few months ago I managed to enlarge the maintenance windows for autotask on a pluggable database, this way:

BEGIN
  dbms_scheduler.disable(
    name  => 'WINDOW_NAME');
  dbms_scheduler.set_attribute(
    name      => 'WINDOW_NAME',
    attribute => 'DURATION',
    value     => numtodsinterval(6, 'hour'));
  dbms_scheduler.enable(
    name => 'WINDOW_NAME');
END;
/

This was what I got:


WINDOW_NAME      START_TIME                               DURATION
---------------- ---------------------------------------- ---------------
THURSDAY_WINDOW  08-JUL-21 10.00.00.241279 PM +02:00      +000 06:00:00
FRIDAY_WINDOW    09-JUL-21 10.00.00.241279 PM +02:00      +000 06:00:00
SATURDAY_WINDOW  10-JUL-21 10.00.00.241279 PM +02:00      +000 06:00:00
SUNDAY_WINDOW    11-JUL-21 10.00.00.241279 PM +02:00      +000 06:00:00
MONDAY_WINDOW    12-JUL-21 10.00.00.241279 PM +02:00      +000 06:00:00
TUESDAY_WINDOW   13-JUL-21 10.00.00.241279 PM +02:00      +000 06:00:00
WEDNESDAY_WINDOW 14-JUL-21 10.00.00.241279 PM +02:00      +000 06:00:00

But now, on that same pluggable db I’m noticing that since August 24th stats jobs are being stopped due to the end of the window:

TASK_NAME                 STATUS     CURRENT_JOB_NAME          LAST_TRY_DATE                       LAST_TRY_R
------------------------- ---------- ------------------------- ----------------------------------- ----------
gather_stats_prog         ENABLED                              12-SEP-21 03.00.09.858615 AM +02:00 STOPPED AT
                                                                                                    END OF MA
                                                                                                   INTENANCE
                                                                                                   WINDOW

auto_space_advisor_prog   ENABLED                              12-SEP-21 12.33.31.490404 AM +02:00 SUCCEEDED
AUTO_SQL_TUNING_PROG      ENABLED                              11-SEP-21 11.00.22.422336 PM +02:00 SUCCEEDED

At first I thought that it might be caused by some performance problem, but then I noticed that the jobs were still during 4 hours (default windows duration):

CLIENT_NAME                         JOB_NAME                  JOB_STATUS JOB_START_TIME                             JOB_DURATION
----------------------------------- ------------------------- ---------- ------------------------------------------ ---------------
auto optimizer stats collection     ORA$AT_OS_OPT_SY_9601     STOPPED    07-SEP-21 10.00.19.825083 PM EUROPE/VIENNA +000 03:59:44
auto optimizer stats collection     ORA$AT_OS_OPT_SY_9621     STOPPED    08-SEP-21 10.00.11.786102 PM EUROPE/VIENNA +000 03:59:53

I then noticed that the maintenance windows duration was still set to 4 hours on the container database:

WINDOW_NAME      START_TIME                               DURATION
---------------- ---------------------------------------- ---------------
SUNDAY_WINDOW    12-SEP-21 10.00.00.235575 PM +02:00      +000 04:00:00
MONDAY_WINDOW    13-SEP-21 10.00.00.235575 PM +02:00      +000 04:00:00
TUESDAY_WINDOW   14-SEP-21 10.00.00.235575 PM +02:00      +000 04:00:00
WEDNESDAY_WINDOW 15-SEP-21 10.00.00.235575 PM +02:00      +000 04:00:00
THURSDAY_WINDOW  16-SEP-21 10.00.00.235575 PM +02:00      +000 04:00:00
FRIDAY_WINDOW    17-SEP-21 10.00.00.235575 PM +02:00      +000 04:00:00
SATURDAY_WINDOW  18-SEP-21 10.00.00.235575 PM +02:00      +000 04:00:00

Should I modify the duration on the container too?

Thank you.