ORA-01306: dbms_logmnr.start_logmnr() must be invoked before
selecting from v$logmnr_contents
- 2 Answers
- 8353 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-38414: invalid datatype for the attribute string
NPL-00419: received ASN.1 object identifier with sub-identifier that is too large
ORA-00065: initialization of FIXED_DATE failed
ORA-31525: could not find column string in CDC change table string.string
ORA-13342: an arc geometry has fewer than three coordinates
SQL*Loader-00280: table string is a temporary table
PLS-00411: Number of values in aggregate and in subquery don't match
ORA-28183: proper authentication not provided by proxy
ORA-00027: cannot kill current session
ORA-09291: sksachk: invalid device specified for archive destination
ORA-01987: client os username is too long
ORA-01488: invalid nibble or byte in the input data
Oracle Errors 
