Answer / guest

Cause: Conflicting changes to objects in source and target
schemas. This might happen if an object has been changed in
both schemas.

Action: Do sync/swap/validation_check with
ignore_conflict/force_sync parameters(TRUE), or Re-start
clone from scratch.

Please add more information about this Error

ORA-19506: failed to create sequential file, name="string", parms="string"

1 Answers  

---

ORA-19614: archivelog thread string sequence string not found in backup set

1 Answers  

---

NZE-28801: invalid object type

1 Answers  

---

TNS-00506: Operation would block

1 Answers  

---

ORA-16180: number processes specified for MAX_PARALLEL_SERVERS is too small

1 Answers  

---

PCB-00500: No EXEC SQL CONTEXT USE statement encountered

1 Answers  

---

ORA-26084: direct path context already finished

0 Answers  

---

ORA-27089: unable to release advisory lock

1 Answers  

---

PLS-00633: RETURN statement in a pipelined function cannot contain an expression

1 Answers  

---

ORA-13115: [string]_EDGE$ table does not exist

1 Answers  

---

PLS-00623: FLOAT precision constraint must be between 1 and 126

1 Answers  

---

ORA-30394: source statement identical to the destination statement

1 Answers  

---