Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-31477: could not detach LogMiner session during cleanup
- 1 Answers
- 2776 Views
- I also Faced
- E-Mail Answers
Answer Posted / guest
Cause: Failure during detach from a LogMiner session during
advance of an asynchronous change set. This is an internal
error. This exception is raised when a previous exception
occurred during the internal protocol with LogMiner, after
which Change Data Capture attempted to detach the LogMiner
session as part of recovery. The detach session also failed
Action: Contact Oracle Corporation
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
IMG-02003: 2FF03 - incorrect color histogram feature specification
ORA-26076: cannot set or reset value after direct path structure is allocated
NZE-28868: Peer certificate chain check failed.
ORA-26082: load of overlapping segments on table string.string is not allowed
ORA-26094: stream format error: input column overflow
ORA-26095: unprocessed stream data exists
if the lengths of two wires are same and the area of cross sections is 4:7 then what will be the ratio of current passing through these wires
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
RMAN-05017: no copy of datafile number found to recover
IMP-00070: Lob definitions in dump file are inconsistent with database.
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
IMP-00064: Definition of LOB was truncated by export
ORA-26028: index string.string initially in unusable state
