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 |
ORA-00399: corrupt change description in redo log
ORA-13769: Snapshots string and string do not exist.
RMAN-08059: media recovery failed
LPX-00205: expected "
ORA-23337: priority or value not in priority group string
ORA-25010: Invalid nested table column name in nested table clause
ORA-22616: image is not of Oracle 8.1 format
SQL*Loader-00918: The catalog must be loaded (as SYS) for SQL*Loader to be used
TNS-01047: Old Parameter File string
ORA-02057: 2PC: string: bad two-phase recovery state number string from string
ORA-06809: TLI Driver: could not clear the IPX ethernet SAP at init
ORA-23435: cannot create an updatable ROWID materialized view with LOB columns