Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...


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-36204: (XSAGOP04N) In AGGMAP workspace object, the NAOPERATOR string must be HFIRST, HLAST or HEVEN.

1 Answers  


QSM-01014: top level operator in WHERE clause of the query is an OR

1 Answers  


ORA-00953: missing or invalid index name

1 Answers  


ORA-25506: resource manager has not been continuously on in some instances

1 Answers  


ORA-31425: subscription does not exist

1 Answers  


ORA-29355: NULL or invalid string argument specified

1 Answers  


ORA-38721: Invalid file number.

1 Answers  


NZE-29193: no CRL found using CRLDP mechanism

1 Answers  


ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST with keep attributes

2 Answers  


ORA-12801: error signaled in parallel query server string

1 Answers  


ORA-36962: (XSRELTBL08) string is not a valid qualified data reference for dimension workspace object.

1 Answers  


ORA-07842: sllfcl: SYS$CLOSE failure

1 Answers  


Categories