Answer / guest

Cause: An attempt was made to use a date expression whose
format does not fully (i.e. day, month, and year (including
century)) specify a date as a partition bound for a DATE
column. The format may have been specified explicitly (using
TO_DATE() function) or implicitly (NLS_DATE_FORMAT).

Action: Ensure that date format used in a partition bound
for a DATE column supports complete specification of a date
(i.e. day, month, and year (including century)). If
NLS_DATE_FORMAT does not support complete (i.e. including
the century) specification of the year, use TO_DATE() (e.g.
TO_DATE('01-01-1999', 'MM-DD-YYYY') to fully express the
desired date.

Please add more information about this Error

ORA-01102: cannot mount database in EXCLUSIVE mode

1 Answers  

---

ORA-13905: Critical or warning threshold have incorrect values

1 Answers  

---

DRG-11218: malformed mail line, line string

1 Answers  

---

O2I-00130: Invalid Java file name

1 Answers  

---

ORA-30734: cannot specify scope constraint on ref column with rowid

1 Answers  

---

ORA-16116: no work available

1 Answers  

---

ORA-22893: constraint can be specified only for REF columns

1 Answers  

---

PLS-00581: inheritance is not supported for opaque types

1 Answers  

---

ORA-06762: TLI Driver: error reading orderly release

1 Answers  

---

ORA-27020: named devices not supported

1 Answers  

---

ORA-07704: error in archive text: need ':' after device name

1 Answers  

---

ORA-01041: internal error. hostdef extension doesn't exist

1 Answers  

---