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-01082: 'row_locking = always' requires the transaction processing option

1 Answers  

---

ORA-02266: unique/primary keys in table referenced by enabled foreign keys

1 Answers  

---

ORA-00362: member is required to form a valid logfile in group string

1 Answers  

---

TNS-12215: TNS:poorly formed PREFERRED_NAVIGATORS Addresses in TNSNAV.ORA

1 Answers  

---

ORA-12056: invalid REFRESH method

1 Answers  

---

ORA-25229: error on transformation of message string string

1 Answers  

---

PLS-01707: In positioned DELETE or UPDATE statement, table must be identified in specification of cursor

1 Answers  

---

ORA-03134: Connections to this server version are no longer supported.

1 Answers  

---

ORA-14459: missing GLOBAL keyword

2 Answers  

---

ORA-26059: Data is too large for column string

1 Answers  

---

NNL-00930: Requests refused, unknown data type: number

1 Answers  

---

TNS-01027: Listener Trace File string

1 Answers  

---