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-07202: sltln: invalid parameter to sltln.

1 Answers  

---

PCC-00120: File I/O error during code generation

1 Answers  

---

ORA-24303: call not supported in non-deferred linkage

1 Answers  

---

QSM-02036: in-list present in mv

1 Answers  

---

ORA-00027: cannot kill current session

1 Answers  

---

---

ORA-14629: cannot drop the only subpartition of a partition

1 Answers  

---

ORA-38752: file string does not exist

1 Answers  

---

TNS-01098: TIMESTAMP * CONNECT DATA * ADDRESS * [PRESENTATION *] COMMAND * ERROR TIMESTAMP * [INSTANCE NAME *] [ADDRESS *] [PRESENTATION *] COMMAND * ERROR -------------------------------------------------------------------------------

1 Answers  

---

ORA-08236: smsget: cannot share subcube with listener

1 Answers  

---

ORA-12350: database link being dropped is still mounted

1 Answers  

---

EXP-00064: %s is an inner nested table and cannot be exported.

1 Answers  

---

ORA-00160: global transaction length string is greater than maximum (string)

1 Answers  

---