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

RMAN-20221: ambiguous controlfile copy name

1 Answers  

---

ORA-01174: DB_FILES is string buts needs to be string to be compatible

1 Answers  

---

PLS-01711: A SELECT statement may not contain ORDER_BY, HAVING, or GROUP_BY clause

1 Answers  

---

ORA-12994: drop column option only allowed once in statement

1 Answers  

---

ORA-30503: system triggers cannot have a REFERENCING clause

1 Answers  

---

RMAN-06073: file header is corrupt for datafile string

1 Answers  

---

ORA-26571: %s.string.string: number of arguments (string) does not match replication catalog

1 Answers  

---

ORA-13271: error allocating memory for geometry object

1 Answers  

---

PLS-00433: inconsistent package STANDARD

1 Answers  

---

DRG-11306: operation cannot be performed on a policy

1 Answers  

---

ORA-12448: policy string not applied to schema string

1 Answers  

---

LPX-00208: unknown DTD keyword "~s"

1 Answers  

---