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

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

ORA-21709: cannot refresh an object that has been modified

1 Answers  

---

ORA-09941: Version of orapasswd or installer is older than file.

1 Answers  

---

RMAN-06533: KEEP ... NOLOGS option is not supported when database is open

2 Answers  

---

SQL*Loader-00925: Error while string

1 Answers  

---

ORA-02264: name already used by an existing constraint

1 Answers  

---

---

ORA-12005: may not schedule automatic refresh for times in the past

2 Answers  

---

ORA-01370: Specified restart SCN is too old

1 Answers  

---

DRG-12603: CTXSYS does not own user datastore procedure: string

1 Answers  

---

RMAN-06750: SPFILE cannot be backed up by proxy.

1 Answers  

---

ORA-03126: network driver does not support non-blocking operations

1 Answers  

---

ORA-15105: missing or invalid FAILGROUP name

1 Answers  

---

NID-00410: Reversion of database changes failed during validation - database is intact.

1 Answers  

---