ORA-01353: existing Logminer session
- 1 Answers
- 2858 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-31217: DBMS_LDAP: PL/SQL - Invalid LDAP newparent.
ORA-30727: duplicate referential constraint for a REF column
TNS-12622: TNS:event notifications are not homogeneous
ORA-22280: no more buffers available for operation
ORA-31062: Cannot delete an unsaved resource
ORA-06567: invalid number of values specified
ORA-12649: Unknown encryption or data integrity algorithm
RMAN-20311: ambiguous proxy copy handle
ORA-13200: internal error [string] in spatial indexing.
CLSR-00525: prsr initialization failed
ORA-10583: Can not recovery file string renamed as missing during test recovery
ORA-34722: (NLSCHARSET05) CAUTION: Character data loss in character set conversion from string to string
Oracle Errors 
