Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-01353: existing Logminer session
- 1 Answers
- 3388 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-01205: not a data file - type number in header is string
ORA-16716: clearing parameter LOG_ARCHIVE_DEST failed
RMAN-10002: ORACLE error: string
ORA-31051: Requested access privileges not supported
ORA-37042: (XSACQUIRE_DEP_DEADLOCK) Cannot wait to acquire composite, concat, dimension map, or internal partition workspace object since doing so would cause a deadlock.
ORA-22866: default character set is of varying width
QSM-01044: join back attempted on a view for string
ORA-12720: operation requires database is in EXCLUSIVE mode
ORA-19300: Error occurred in uri processingstring
ORA-26715: time limit reached
ORA-16583: bad Data Guard Connection Process DRCX state
ORA-07401: sptrap: cannot restore user exception handlers.
Oracle Errors 
