Cause: A select was issued from v$logmnr_contents without first invoking t

ORA-01306: dbms_logmnr.start_logmnr() must be invoked before
selecting from v$logmnr_contents

Question Posted / guest

2 Answers
9597 Views
Wipro, I also Faced
E-Mail Answers

Answer Posted / guest

Cause: A select was issued from v$logmnr_contents without
first invoking the dbms_logmnr.start_logmnr() procedure.

Action: Invoke the dbms_logmnr.start_logmnr() procedure
before issuing a select from the v$logmnr_contents view.

Please add more information about this Error

Is This Answer Correct ?

4 Yes

1 No

Post New Answer View All Answers

Please Help Members By Posting Answers For Below Questions

IMG-02003: 2FF03 - incorrect color histogram feature specification

1767

IMP-00070: Lob definitions in dump file are inconsistent with database.

1801

ORA-16627: No standby databases support the overall protection mode.

4039

IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created

1667

ORA-16626: failed to enable specified object

2275

When i am connect database through toad,one error occured. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor. plz help me thanks advance.............

2864

ORA-26082: load of overlapping segments on table string.string is not allowed

1819

invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity

3438

ORA-26084: direct path context already finished

1999

ORA-26095: unprocessed stream data exists

3642

ORA-26029: index string.string partition string initially in unusable state

2233

ORA-16516: The current state is invalid for the attempted operation.

8879

IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier

3226

NZE-28868: Peer certificate chain check failed.

2864

ORA-26030: index string.string had string partitions made unusable due to:

1990