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-00399: corrupt change description in redo log

1 Answers  


ORA-13769: Snapshots string and string do not exist.

1 Answers  


RMAN-08059: media recovery failed

1 Answers  


LPX-00205: expected "

1 Answers  


ORA-23337: priority or value not in priority group string

1 Answers  


ORA-25010: Invalid nested table column name in nested table clause

1 Answers  


ORA-22616: image is not of Oracle 8.1 format

1 Answers  


SQL*Loader-00918: The catalog must be loaded (as SYS) for SQL*Loader to be used

1 Answers  


TNS-01047: Old Parameter File string

1 Answers  


ORA-02057: 2PC: string: bad two-phase recovery state number string from string

1 Answers  


ORA-06809: TLI Driver: could not clear the IPX ethernet SAP at init

1 Answers  


ORA-23435: cannot create an updatable ROWID materialized view with LOB columns

1 Answers  


Categories