RE: dbms_scheduler_job_run_details Question

forgive my rust, this could be completely wrong:  

Check the OS date of the log file.

Does the time at GMT plus the duration of the job run add up to the log_date?  

Does that make it easier to find (or verify deleted) of this particular log at the OS level?  

Since it is so seductively close to an exact hour, could it be that the job is an auto-rescheduled job that was created during daylight savings time?  

I'm too lazy to look up the description of the meaning of the log_date as documented for that view. My very rusty view is that is the OS time of the last write to that log.  

mwf  

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Scott Canaan
Sent: Tuesday, January 25, 2022 3:44 PM
To: 'oracle-l_at_freelists.org'
Subject: dbms_scheduler_job_run_details Question  

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

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