ORA-27419: unable to determine valid execution date from
repeat interval
Answers were Sorted based on User's Feedback
Answer / senthilora
Two of my jobs have failed with the same error.
They were using the following scheduled clauses:
'FREQ=HOURLY;BYMINUTE=0'.
I scheduled them to run for 3 days by setting up start_date
and end_date attribute of scheduler.
They ran successfully for every hours for 3 days and failed
on 3rd day when it reached the end_date (time).
I think, this error can be read as a alarm note to note that
the scheduler has reached the end_date and so the jobs which
are all using this scheduler will not be executed here after.
Regards
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / guest
Cause: The specified repeat interval contained conflicting
clauses that made it impossible to ever find a matching
date, e.g., 'FREQ=YEARLY;BYMONTH=FEB;BYMONTHDAY=31'.
Alternatively, the scheduler reached its maximum number of
attempts to try to find a valid execution date. This occurs
when theoretically there is a valid execution date far in
the future, but the scheduler took too many attempts to
determine this date.
Action: Remove the conflicting clauses, or simplify the
repeat interval so that it is easier to determine the next
execution date.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 1 No |
TNS-02505: Authentication: null context pointer provided
TNS-01165: Spawn alias has no program name set in it
NNL-00932: Requests refused, type syntax mismatch: number
ORA-12547: TNS:lost contact
ORA-02160: index-organized table can not contain columns of type LONG
ORA-27032: failed to obtain file size limit
RMAN-12016: using channel string
ORA-36993: (XSRELGID10) OBJECT workspace object must be a VARIABLE, RELATION, or a numeric SURROGATE DIMENSION based on the level dimension workspace object.
PCB-00576: PLS-number: string
ORA-06803: TLI Driver: the IPX device file could not be opened
IMG-00518: invalid value for height or width
RMAN-04013: must connect before startup