ORA-01353: existing Logminer session
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-23293: Cannot rename a column which is part of a join index
ORA-23344: constraint (string.string) does not exist
ORA-14076: submitted alter index partition/subpartition operation is not valid for local partitioned index
IMG-00899: signature cannot be generated
ORA-12438: repeated policy option: string
ORA-06760: TLI Driver: timeout reading orderly release
RMAN-06030: the DELETE [ALL] INPUT option may not be used with a datafile backup set
ORA-26501: RepAPI operation failure
ORA-01119: error in creating database file 'string'
DRG-11306: operation cannot be performed on a policy
RMAN-07521: cannot create recovery catalog in database version string; version string required
ORA-23418: cannot unregister the propagator who is currently in use