Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-02436: date or system variable wrongly specified in
CHECK constraint
- 1 Answers
- 4615 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 |
ORA-16703: cannot set the property while the database is enabled
AMD-00118: output file "string" already exists
PCB-00238: Element of this table group item host variable cannot be a table
ORA-07303: ksmcsg: illegal database buffer size.
ORA-14063: Unusable index exists on unique/primary constraint key
ORA-07491: scgrcl: cannot cancel lock request.
ORA-28277: LDAP search, while authenticating global user with passwords, failed.
ORA-12047: PCT FAST REFRESH cannot be used for materialized view "string"."string"
NZE-29019: The protocol version is incorrect.
SQL*Loader-00620: Initial enclosure character not found
ORA-33998: (MODCOMP12) You cannot use both workspace object and workspace object as model dimensions, because workspace object is a surrogate of workspace object.
RMAN-08015: datafile string switched to datafile copy
Oracle Errors 
