Re: the time zone of systimestamp is not match the user_scheduler_jobs

Joan,
have the jobs failed to run completely or have the actions triggered by the jobs failed? It would be a different matter. I don't reckon the difference between the TZ used by your SQL client and the TZ showed in dbms_scheduler is part of the problem, unless it is hinting a problem under the covers.

[image: Pythian] <http://www.pythian.com/> *Jose Rodriguez* | Oracle Project Engineer | [image: LinkedIn] <https://www.linkedin.com/company/pythian> *t* +1 613 565 8696 <+1+613+565+8696> *ext.* 1393 *m* +34 607 55 49 91 <+34+607+55+49+91>
jrodriguez2_at_pythian.com
*www.pythian.com* <https://www.pythian.com/> [image: Pythian] <https://www.pythian.com/email-footer-click>

On Wed, 12 Dec 2018 at 15:56, Joan Hsieh <joanhsieh08_at_gmail.com> wrote:

> Hi Listers,
>
> we have some dbms_scheduler_jobs failed due to the timestamp is not
> correct. it throw out tons of errors of ORA-08186: invalid timestamp
> specified .
> The last_start_date from user_scheduler_jobs returns -4:00,
> 12-DEC-18 10.43.17.198623 AM -04:00
>
> but the systimestamp from dual returns -5:00. what we should do to get it
> sync.?
>
> SQL> select systimestamp from dual;
>
> SYSTIMESTAMP
> ---------------------------------------------------------------------------
> 12-DEC-18 09.47.28.000075 AM -05:00
>
> Thank you so much.
>
> Joan
>
>

-- 


--






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