Answer / guest

Cause: An attempt was made to use a date constant or system
variable, such as USER, in a check constraint that was not
completely specified in a CREATE TABLE or ALTER TABLE
statement. For example, a date was specified without the
century.

Action: Completely specify the date constant or system
variable. Setting the event 10149 allows constraints like
"a1 > '10-MAY-96'", which a bug permitted to be created
before version 8.

Please add more information about this Error

PLS-00102: parser stack overflow because nesting is too deep

1 Answers  

---

ORA-02053: transaction string committed, some remote DBs may be in-doubt

1 Answers  

---

ORA-19560: %s is not a valid device limit

1 Answers  

---

PCC-00012: Not in a declare section at line number in file string

1 Answers  

---

NNL-00531: flush_name <name> : removes a name from caches along a route to an authoritative server

1 Answers  

---

---

ORA-16759: Resource guard unable to start logical apply engine with initial SCN

1 Answers  

---

ORA-32508: no such watchpoint id

1 Answers  

---

SQL*Loader-00294: invalid name % specified in TREAT AS clause

1 Answers  

---

DRG-11221: Third-party filter indicates this document is corrupted.

1 Answers  

---

ORA-01031: insufficient privileges

1 Answers  

---

PCC-02393: SQL statement found inside an EXEC SQL DECLARE SECTION

1 Answers  

---

ORA-02484: Invalid _trace_buffers parameter specification (string)

1 Answers  

---