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

PLS-01463: STDDEV is not a standard set function

1 Answers  

---

RMAN-06187: controlfile copy string not found or out of sync with catalog

1 Answers  

---

ORA-22150: variable-length array has not been initialized

1 Answers  

---

CLSR-00522: Resource string is not registered

1 Answers  

---

ORA-24361: basic bind call not invoked before invoking advanced bind call

1 Answers  

---

ORA-38728: Cannot FLASHBACK DATABASE to the future.

1 Answers  

---

TNS-02519: no appropriate key-negotiation parameters

1 Answers  

---

NNO-00263: error from configuration database

1 Answers  

---

KUP-04017: OS message: string

1 Answers  

---

KUP-03009: OCI error getting column name.

1 Answers  

---

PCC-02388: Arrays not allowed in FROM/WHERE clause of SELECT statement

1 Answers  

---

NNL-00898: Responses sent: number

1 Answers  

---