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

PROC-00106: Unidentified component error

1 Answers  

---

NCR-01018: NCRS: Encryption failure.

1 Answers  

---

TNS-12204: TNS:received data refused from an application

1 Answers  

---

ORA-24024: Internal error in DBMS_AQ_IMP_INTERNAL.string [string] [string]

1 Answers  

---

DGM-17002: Primary database can not be removed.

1 Answers  

---

PCC-02373: Invalid declaration in EXEC SQL DECLARE section

1 Answers  

---

ORA-16061: Log file status has changed

1 Answers  

---

PCC-02151: Line number column number file string:

1 Answers  

---

ORA-24156: duplicate table alias string

1 Answers  

---

ORA-01088: cannot shut down ORACLE while active processes exist

1 Answers  

---

ORA-12170: TNS:Connect timeout occurred

1 Answers  

---

ORA-19361: ONLINE option not allowed with this type of index

1 Answers  

---