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

PCC-02334: SQL identifier was not declared as a cursor

1 Answers  

---

ORA-25533: FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is specified

2 Answers  

---

ORA-13528: name (string) is already used by an existing baseline

1 Answers  

---

ORA-09312: slspool: error spooling file to printer

1 Answers  

---

ORA-25443: duplicate column value for table alias: string, column number: string

1 Answers  

---

---

TNS-12520: TNS:listener could not find available handler for requested type of server

1 Answers  

---

SQL*Loader-00417: SQL string (on column string) not allowed in direct path.

1 Answers  

---

PLS-00386: type mismatch found at 'string' between FETCH cursor and INTO variables

1 Answers  

---

O2F-00316: An unexpected token was seen at the end of a type specification

1 Answers  

---

ORA-19625: error identifying file string

1 Answers  

---

LSX-00016: schema and instance document have incompatible character sets

1 Answers  

---

PLS-00490: illegal statement

1 Answers  

---