ORA-01306: dbms_logmnr.start_logmnr() must be invoked before
selecting from v$logmnr_contents
- 2 Answers
- 8371 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 |
SQL*Loader-00953: Error shipping read buffer across 2-task
SQL*Loader-00945: record size number too large for direct path
ORA-25507: resource manager has not been continuously on
NID-00101: LOGFILE (string) not accessible
ORA-13201: invalid parameters supplied in CREATE INDEX statement
NNF-02005: NIS key string does not exist in map string
ORA-00080: invalid global area specified by level string
QSM-01010: table(s) in the query not found in materialized view, string
ORA-02203: INITIAL storage options not allowed
ORA-14602: SUBPARTITION TEMPLATE is legal only for a composite partitioned table
ORA-14165: MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations
ORA-16018: cannot use string with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST
Oracle Errors 
