My Oracle Support Banner

Default Maintenance Tasks Starting Before Maintenance Window (Doc ID 1594096.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Information in this document applies to any platform.
***Checked for relevance on 29-DEC-2016***

Symptoms

Default database maintenance jobs that are not running per the scheduled start date of the window. They run within the window, the problem is that the schedule start of the
window is not honoring the schedule start time. The jobs launch at 16:30 CST when they should start at 22:00.

Changes

 1) SQL> SELECT DBTIMEZONE FROM DUAL;
DBTIME
------
-06:00

SQL> SQL> select systimestamp from dual;

SYSTIMESTAMP
---------------------------------------------------------------------------
30-SEP-13 10.06.03.503652 AM -05:00

$ date +"%c"
Tue 01 Oct 2013 10:00:06 PM GMT


CST is -6 from GMT, CDST (daylight savings, current time) is -5. So when select CST it lists it as -6 from GMT. When set the time, the timezone windows switches from -6 to -5 because we're currently in Daylight savings time (-5).

2) The compute nodes are set to GMT, the databases are being set to CST. So when you select sysdate from dual in the db, you get CST if you do a date from the OS you get GMT time.

3) TZ was not set. 

4) Dropping the maintenance window and recreating did not help.

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
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.