Answer / guest

Cause: After the job parameters and filters were applied,
the job specified by the user did not reference any objects.

Action: Verify that the mode of the job specified objects to
be moved. For command line clients, verify that the INCLUDE,
EXCLUDE and CONTENT parameters were correctly set. For
DBMS_DATAPUMP API users, verify that the metadata filters,
data filters, and parameters that were supplied on the job
were correctly set.

Please add more information about this Error

ORA-25217: enqueue failed, visibility must be IMMEDIATE for queue string.string

1 Answers  

---

ORA-23334: column string does not exist in table or column group

1 Answers  

---

ORA-01080: error in shutting down ORACLE

1 Answers  

---

RMAN-08040: full resync skipped, controlfile is not current or backup

1 Answers  

---

ORA-19761: block size string is not valid for change tracking file

1 Answers  

---

---

ORA-29539: Java system classes already installed

1 Answers  

---

ORA-13114: [string]_NODE$ table does not exist

1 Answers  

---

ORA-16207: Logical standby dictionary build not permitted.

1 Answers  

---

ORA-16107: all log data from primary has been processed

1 Answers  

---

DRG-11204: user filter command is too long

1 Answers  

---

ORA-01724: floating point precision is out of range (1 to 126)

1 Answers  

---

QSM-02150: select lists must be identical across the UNION operator

1 Answers  

---