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

NZE-29226: No matching private key found.

1 Answers  

---

ORA-28106: input value for argument #string is not valid

1 Answers  

---

ORA-06973: X.25 Driver: invalid buffer size

1 Answers  

---

ORA-16065: remote archival disabled at standby destination

1 Answers  

---

PLS-00104: empty argument list in call of procedure 'string' must be omitted

1 Answers  

---

ORA-01313: LogMiner dictionary column type different from specified type

1 Answers  

---

ORA-32019: The parameter SPFILE cannot be updated in the server parameter file.

1 Answers  

---

ORA-00385: cannot enable Very Large Memory with new buffer cache parameters

1 Answers  

---

NNL-00520: Changes an existing name's TTL

1 Answers  

---

ORA-01213: MAXINSTANCES may not exceed string

1 Answers  

---

ORA-36691: (NTEXTCNV02) Invalid escape sequence in argument to UNISTR function: string.

1 Answers  

---

ORA-01933: cannot create a stored object using privileges from a role

1 Answers  

---