Answer / guest

Cause: There was an error originating from this synchronous
change table. One possible cause is that schema redefinition
has occurred on the source table and one or more columns in
the change table are now a different type than corresponding
source columns. Another possible cause is that there is a
problem accessing the synchronous change table.

Action: Check further error messages in stack for more
detail about the cause. If there has been schema
redefinition, drop and recreate the synchronous change table.

Please add more information about this Error

ORA-03245: Tablespace has to be dictionary managed, online and permanent to be able to migrate

1 Answers  

---

NNO-00264: configuration database query returned no data

1 Answers  

---

ORA-36258: (XSAGINFO00) When the AGGMAPINFO function is called, workspace object must be an AGGMAP.

1 Answers  

---

SQL-02133: Unable to initialize process for use with threads

1 Answers  

---

DGM-16946: Site "string" was not found

1 Answers  

---

ORA-27071: unable to seek to desired position in file

1 Answers  

---

ORA-39090: Cannot add devices to file oriented job.

1 Answers  

---

ORA-27160: process requested to perform operation

1 Answers  

---

UDI-00014: invalid value for parameter, 'string'

1 Answers  

---

IMP-00029: cannot qualify table name by owner (string), use FROMUSER parameter

1 Answers  

---

SQL*Loader-00602: Maximum converted length number of column string is too big for bind array

1 Answers  

---

KUP-04050: error while attempting to allocate number bytes of memory

1 Answers  

---