Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-01353: existing Logminer session
- 1 Answers
- 3503 Views
- I also Faced
- E-Mail Answers
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
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-10574: Test recovery did not corrupt any data block
ORA-31624: operation string not allowed when job in string state
ORA-31423: change table string does not contain column string
ORA-00267: name of archived log file not needed
PLS-00924: native compilation is not supported on this platform
ORA-03211: The segment does not exist or is not in a valid state
ORA-26010: Column string in table string is NOT NULL and is not being loaded
ORA-08233: smsdes: cannot unmap SGA
TNS-03601: Failed in route information collection
ORA-13275: spatial index creation failure on unsupported type
ORA-09821: Numeric label is not valid
KUP-03016: length specified for FIXED records must be greater than 0
Oracle Errors 
