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

DRG-50924: PL/SQL inside PL/SQL not supported

1 Answers  

---

RMAN-06518: backup will be obsolete on date string

1 Answers  

---

ORA-19769: missing FILE keyword

1 Answers  

---

ORA-16592: missing field "string" in document

1 Answers  

---

ORA-14274: partitions being merged are not adjacent

1 Answers  

---

QSM-01043: join back attempted on a table to the RHS of a semi or anti join for string

1 Answers  

---

ORA-19759: block change tracking is not enabled

1 Answers  

---

ORA-02211: invalid value for PCTFREE or PCTUSED

1 Answers  

---

ORA-39119: worker process interrupt for delete worker processes call by master process

1 Answers  

---

ORA-02459: Hashkey value must be a positive integer

1 Answers  

---

EXP-00033: Could not find environment character set

1 Answers  

---

QSM-01039: selection present on right hand side of an outer join

1 Answers  

---