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@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Scott Canaan
Sent: Tuesday, January 25, 2022 3:44 PM
To: 'oracle-l@xxxxxxxxxxxxx'
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
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
<mailto:srcdco@xxxxxxx> srcdco@xxxxxxx | 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.
