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

NNL-00931: Requests refused, no cached meta-data: number

1 Answers  

---

ORA-09870: spini: failure initializing maximum number of open files.

1 Answers  

---

ORA-25192: invalid option for an index-organized table

1 Answers  

---

DRG-10828: token string is longer than maximum length for column string

1 Answers  

---

ORA-03219: Tablespace 'string' is dictionary-managed, offline or temporary

1 Answers  

---

DRG-11207: user filter command exited with status string

1 Answers  

---

ORA-26005: Invalid handle for direct path load

1 Answers  

---

NZE-29095: Index is not correct.

1 Answers  

---

QSM-00799: the user-defined workload table string cannot be found

1 Answers  

---

ORA-31056: The document being inserted does not conform to string

1 Answers  

---

ORA-32576: missing TYPE keyword

1 Answers  

---

ORA-01647: tablespace 'string' is read only, cannot allocate space in it

2 Answers  

---