Answer / guest

Cause: User specified an invalid operation name on an
DBMS_DATAPUMP.OPEN API or an invalid operation name was
specified in the master table for a restart API.

Action: Correct the operation name and recreate the job.

Please add more information about this Error

RMAN-08060: unable to find archive log

1 Answers  

---

ORA-39702: database not open for UPGRADE or DOWNGRADE

1 Answers  

---

ORA-07261: spdde: kill error, unable to send signal to process.

1 Answers  

---

ORA-19207: scalar parameter string of XMLELEMENT cannot have an alias.

1 Answers  

---

ORA-09774: osnmui: cannot send break message

1 Answers  

---

ORA-06953: Not enough virtual memory

1 Answers  

---

ORA-29704: cannot specify ACTIVE_INSTANCE_COUNT in 8.1.5 or earlier release

1 Answers  

---

ORA-09885: osnTXtt: cannot create TXIPC channel

1 Answers  

---

ORA-19400: System type conflict with object SYS.string

1 Answers  

---

ORA-02306: cannot create a type that already has valid dependent(s)

1 Answers  

---

ORA-16610: one or more resources have warnings

1 Answers  

---

SQL*Loader-00655: cannot load object-relational XML attribute using direct path

1 Answers  

---