Answer / guest

Cause: User attempted to execute the DROP_CHANGE_TABLE
procedure on a table that is not a CHANGE table. This can
also occur when a CHANGE table object has been orphaned.
CHANGE tables can become orphaned after a
CREATE_CHANGE_TABLE failure or an incomplete DROP_CHANGE_TABLE.

Action: Check spelling. If error was due to an incorrect
name, then retry the procedure using the correct name. To
drop a table that is not a CHANGE table, or an orphaned
CHANGE table, use the DROP TABLE DDL command instead.

Please add more information about this Error

QSM-02024: no GROUP BY clause

1 Answers  

---

ORA-36393: (XSMXCLEA03) When using the CHANGES or CACHE options, you must specify the ALL keyword.

1 Answers  

---

ORA-27490: cannot open disabled window "string.string"

1 Answers  

---

ORA-37012: (XSACQUIRE_TIMEOUT) Object workspace object is locked by another user and the WAIT timed out.

1 Answers  

---

ORA-13635: The value string provided for parameter string cannot be converted to a number.

1 Answers  

---

ORA-13147: failed to generate MBR

1 Answers  

---

ORA-31075: invalid string declaration in XML Schema

1 Answers  

---

ORA-06263: NETNTT: out of memory in pi_connect

1 Answers  

---

O2F-00324: Unable to convert from the database character set to the compiler character set

1 Answers  

---

SQL*Loader-00916: Error checking path homogeneity

1 Answers  

---

ORA-30393: a query block in the statement did not rewrite

1 Answers  

---

ORA-31010: XML element index string exceeds maximum insertion index string

1 Answers  

---