ORA-27419: unable to determine valid execution date from
repeat interval

Answers were Sorted based on User's Feedback



ORA-27419: unable to determine valid execution date from repeat interval..

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

ORA-27419: unable to determine valid execution date from repeat interval..

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

Post New Answer

More Oracle Errors Interview Questions

ORA-38771: unnamed datafile(s) added to controlfile by flashback recovery

1 Answers  


ORA-30505: system triggers should not reference a column in a WHEN clause

1 Answers  


ORA-12821: invalid value for INSTANCES

1 Answers  


O2F-00319: No OUTTYPE file specified

1 Answers  


ORA-00165: migratable distributed autonomous transaction with remote operation is not allowed

1 Answers  






NNF-00110: no values exist

1 Answers  


NZE-29108: Cannot initialize random object.

1 Answers  


ORA-40108: input data contains too few distinct target (string) values

1 Answers  


ORA-19556: required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred

1 Answers  


ORA-04021: timeout occurred while waiting to lock object stringstringstringstringstring

1 Answers  


DRG-50704: Net8 listener is not running or cannot start external procedures

1 Answers  


ORA-32051: mapping service not available

1 Answers  


Categories