As we passed the DST change we found most of our scheduler jobs ran an hour early the first time after the change, then corrected on subsequent runs. Investigating, we found that the jobs’ START_DATE was specified with a time offset rather than a time zone name. When this is the case, those jobs are not DST aware. That’s all standard Oracle stuff and is not a SQL Nav problem in itself.
However …
In creating new or maintaining existing jobs, I have not been able to get SQL Nav to specify a named TZ on the START_DATE. So far I’ve had to resort to manually running dbms_scheduler.set_attribute_null to force the start date to use the scheduler default TZ, which is set at CST6CDT.
Have been working with Oracle for years, but recently started a new job and am pretty new to SQL Nav. Is there a procedural step or a default setting I’m missing, to allow a job setup with SQL Nav to use the scheduler default TZ?
–
Just as an update, it really appears that SQL Nav is doing something with its session vis a vis ‘timestamp with TZ’. Executing the same query from sqlplus on my desktop gives a different result from the executing it within SQL Nav on the same desktop to the same db:
From sqlplus:
SQL> select dbms_scheduler.stime from dual;
STIME
09-NOV-12 01.07.22.124966000 PM US/CENTRAL
SQL>
From SQL Nav
09-NOV-2012 1:06:55.326640000 PM -06:00
and - just for grins - from sqlplus on the database server:
SQL> select dbms_scheduler.stime from dual;
STIME
09-NOV-12 01.06.27.344264000 PM CST6CDT
Message was edited by: estevens_062
Message was edited by: estevens_062