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

EXP-00034: error on rowid: file# number block# number slot# number

1 Answers  

---

NNL-00577: list_domains: list authoritative domains in the region or subtree

1 Answers  

---

TNS-01041: %s parameter "string" set to string

1 Answers  

---

ORA-38410: schema extension not allowed for the table name

1 Answers  

---

ORA-08435: PICTURE MASK missing the leading sign when SIGN IS LEADING specified

1 Answers  

---

NID-00142: Only changing database name, previous attempt changed dbid to number

1 Answers  

---

ORA-02026: missing LINK keyword

1 Answers  

---

LPX-00242: invalid use of ampersand ('&') character (use &)

1 Answers  

---

UDE-00006: failed to allocate memory of size number

1 Answers  

---

ORA-32730: Command cannot be executed on remote instance

1 Answers  

---

ORA-32001: write to SPFILE requested but no SPFILE specified at startup

1 Answers  

---

ORA-14406: updated partition key is beyond highest legal partition key

1 Answers  

---