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
- 9446 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-12685: Native service required remotely but disabled locally
ORA-01479: last character in the buffer is not Null
ORA-19618: cannot name files after restoreValidate has been called
ORA-23365: site string does not exist
PCC-02416: The Object in an OBJECT GET or SET must not be an array
ORA-24016: cannot create QUEUE_TABLE, user string does not have execute privileges on QUEUE_PAYLOAD_TYPE string.string
PLS-01450: This <value expression> contains a nonconforming data type
PCC-00002: Invalid syntax at column number in line number of file string
PLS-00517: Type mismatch between a select list element 'string' and corresponding table column in INSERT statement with a subquery
ORA-07495: spwat: lm_wait failed.
PLS-01714: ANSI expects a column name not a literal value here
ORA-30352: inconsistent numeric precision or string length
Oracle Errors 
