ORA-01306: dbms_logmnr.start_logmnr() must be invoked before
selecting from v$logmnr_contents
- 2 Answers
- 9676 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 |
AMD-00158: The Workspace "string" is currently open in read-only mode.
SQL*Loader-00281: Warning: ROWS parameter ignored in parallel mode.
ORA-28501: communication error on heterogeneous database link
ORA-22309: attribute with name "string" already exists
RMAN-06113: changed archive log available
PCC-00044: Array size mismatch in INTO/USING. Minimum is: string(number:number)
ORA-29339: tablespace block size string does not match configured block sizes
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
PLS-01705: table specified by a cursor not updatable if cursor specification has a UNION or ORDER_BY
RMAN-00556: could not open CMDFILE "string"
ORA-37086: %s is not a valueset
ORA-24803: illegal parameter value in lob read function
Oracle Errors 
