Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-01306: dbms_logmnr.start_logmnr() must be invoked before
selecting from v$logmnr_contents
- 2 Answers
- 9493 Views
- Wipro, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / 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 |
Answer / ashu
Invoke dbms_logmnr.start_logmnr() procedure
It 'll work
| Is This Answer Correct ? | 1 Yes | 0 No |
ORA-00367: checksum error in log file header
ORA-12522: TNS:listener could not find available instance with given INSTANCE_ROLE
ORA-19651: cannot apply offline-range record to datafile string: SCN mismatch
ORA-28181: proxy 'string' failed to enable one or more of the specified initial roles for client 'string'
ORA-12465: Not authorized for read or write on specified groups or compartments
RMAN-06013: duplicate channel identifier found: string
ORA-31084: error while creating table "string"."string" for element "string"
ORA-28511: lost RPC connection to heterogeneous remote agent using SID=string
ORA-39065: unexpected master process exception in string
ORA-24341: bad mode specified
ORA-12542: TNS:address already in use
NNL-00898: Responses sent: number
Oracle Errors 
