Re: dbms_scheduler_job_run_details Question

All of the date columns in that view
<https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/ALL_SCHEDULER_JOB_RUN_DETAILS.html#GUID-E87CA539-38E8-41A4-B10B-784308A56F02> are type timestamp(6) with time zone. The log_date column most likely has a different timezone offset than the others. Format the columns in your query to show timestamp with time zone to reveal the truth!

Andy

On Tue, Jan 25, 2022 at 2:44 PM Scott Canaan <srcdco_at_rit.edu> wrote:

> I got an inquiry from a customer about the dates in the
> dbms_scheduler_job_run_details view. He is confused as to why the log_date
> is an hour earlier than the req_start_date and actual_start_date. For
> example:
>
>
>
> Log_id log_date
> Job_name
> requested_start_date actual_start_date
>
> 8610130 1/25/2022 4:31:05 AM
> RIT_K0704_BL_GOALS_DBMS_JOB 1/25/2022 5:30:00 AM
> 1/25/2022 5:30:02 AM
>
>
>
> The requested start time is set in the job definition to be 5:30am. I’m
> having trouble explaining why there’s a difference. He has asked me to
> “fix the GMT differential”.
>
>
>
> This is an Oracle 12.1.0.2 database running on Red Hat 7.
>
>
>
> *Scott Canaan ‘88*
>
> *Sr Database Administrator *Information & Technology Services
> Finance & Administration
>
>
> *Rochester Institute of Technology *o: (585) 475-7886 | f: (585) 475-7520
>
> *srcdco_at_rit.edu <srcdco_at_rit.edu>* | c: (585) 339-8659
>
> *CONFIDENTIALITY NOTE*: The information transmitted, including
> attachments, is intended only for the person(s) or entity to which it is
> addressed and may contain confidential and/or privileged material. Any
> review, retransmission, dissemination or other use of, or taking of any
> action in reliance upon this information by persons or entities other than
> the intended recipient is prohibited. If you received this in error, please
> contact the sender and destroy any copies of this information.
>
>
>

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