Answer / guest

Cause: An attempt was made to execute
DBMS_LOGMNR_D.SET_TABLESPACE while a Logminer session(s) was
active.

Action: First cause all Logminer sessions to be closed. A
Logminer session can exist as a result of executing
DBMS_LOGMNR.START_LOGMNR or as the result of using Oracle
features such as Data Guard SQL Apply or Streams which use
Logminer. Next, execute DBMS_LOGMNR_D.SET_TABLESPACE.

Please add more information about this Error

ORA-06260: NETNTT: cannot write to remote process

1 Answers  

---

TNS-01154: SID detected in old format that is no longer supported

1 Answers  

---

PCC-02425: An indicator variable is not required with this attribute

1 Answers  

---

NNO-00624: setting auto-refresh expiration period to number seconds

1 Answers  

---

ORA-16213: ddl encountered, stopping apply engine

1 Answers  

---

ORA-24805: LOB type mismatch

1 Answers  

---

NNL-00407: Alias translations:

1 Answers  

---

ORA-03113: end-of-file on communication channel

1 Answers  

---

ORA-19771: cannot rename change tracking file while database is open

1 Answers  

---

PCC-00122: Input file name and output file name are identical

1 Answers  

---

O2F-00303: No INTYPE file was specified

1 Answers  

---

NZE-28775: file cannot close

1 Answers  

---