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

ORA-01269: Destination parameter string is too long

1 Answers  

---

LSX-00024: unknown attribute group "~S"

1 Answers  

---

ORA-39726: unsupported add/drop column operation on compressed tables

1 Answers  

---

ORA-27014: skgfqpini: translation error while expanding SS_UDMPDIR

1 Answers  

---

ORA-14129: INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints

1 Answers  

---

O2F-00334: A user-defined type is listed more than once in the INTYPE file

1 Answers  

---

RMAN-06025: no backup of log thread number seq number lowscn string found to restore

1 Answers  

---

ORA-13404: invalid ultCoordinate parameter

1 Answers  

---

PLS-00146: duplicate external TRUSTED/UNTRUSTED specification in subprogram expression

1 Answers  

---

ORA-23456: flavor string does not contain "string"

1 Answers  

---

ORA-32813: propagation schedule string already exists

1 Answers  

---

LPX-00308: attribute ~S not found in ~S

1 Answers  

---