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

QSM-00785: the directive string is not supported for task string at this time

1 Answers  

---

ORA-25121: MINIMUM EXTENT value greater than maximum extent size

1 Answers  

---

LFI-01519: llseek() failed(OSD return value = string) in string.

1 Answers  

---

ORA-31412: change set string is disabled and cannot be advanced

1 Answers  

---

RMAN-06436: enter DROP CATALOG command again to confirm catalog removal

1 Answers  

---

NNL-00294: No entries found

1 Answers  

---

PCC-00065: Userid required, but not specified.

1 Answers  

---

ORA-32641: invalid expression in MODEL rule ORDER BY clause

1 Answers  

---

ORA-34143: (MXCGPUT02) You cannot assign values to SURROGATE workspace object because it is type INTEGER.

1 Answers  

---

ORA-33448: (ESDREAD04) Discarding compiled code for workspace object because number now has string data, whereas it had string data when the code was compiled.

1 Answers  

---

CLSS-00100: configuration data access failed for key string

1 Answers  

---

SQL*Loader-00607: partition not empty for INSERT option; table string, partition string

1 Answers  

---