ORA-02436: date or system variable wrongly specified in
CHECK constraint
- 1 Answers
- 3989 Views
- I also Faced
- E-Mail Answers
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
| Is This Answer Correct ? | 0 Yes | 3 No |
TNS-04085: Password not changed since last save.
ORA-13838: invalid ADDRESS value
PROC-00021: Maximum permitted depth of the OCR tree is reached
ORA-01562: failed to extend rollback segment number string
ORA-01968: Only specify RESETLOGS or NORESETLOGS once
SQL-01075: you are currently logged on
ORA-29934: index specified for association is not a domain index
NNL-00341: Trace file name is now string
ORA-22328: object "string"."string" has errors. string
ORA-13770: Baseline "string" does not exist.
ORA-01864: the date is out of range for the current calendar
ORA-09341: scumnt: unable to mount database
Oracle Errors 
