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-19638: file string is not current enough to apply this incremental backup

1 Answers  

---

ORA-07478: scgcmn: cannot get lock status.

1 Answers  

---

NCR-03008: NCRO: Call rejected

1 Answers  

---

NNL-00249: DEFAULT-FORWARDERS-ONLY mode is currently enabled

1 Answers  

---

ORA-31051: Requested access privileges not supported

1 Answers  

---

PCC-02046: CMD-LINE: Unable to open config file:

1 Answers  

---

ORA-16785: The database is not in ARCHIVELOG mode

1 Answers  

---

ORA-00720: ALTER DATABASE RESET COMPATIBILITY command has been de-supported

1 Answers  

---

PCC-02302: cannot open code generation output file "string"

1 Answers  

---

ORA-28168: attempted to grant password-protected role

1 Answers  

---

ORA-02795: Request list is empty

1 Answers  

---

ORA-27159: failure setting process scheduling priority

1 Answers  

---