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
- 9599 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 |
RMAN-06225: shuting down automatic instance string
O2I-00129: No Java file specified
ORA-36664: (XSDPART02) You must specify a partitioning method and one or more partition dimensions when defining a PARTITION TEMPLATE.
ORA-32054: lost communication with FMPUTL process
ORA-28656: incomplete attribute specification
DRG-11866: Please Try `ftp://' Instead Of `file://'
ORA-25442: too many column values for table alias: string
PLS-00625: PARTITION/CLUSTER/ORDER-BY clause can only be used with IN parameters
ORA-33008: (XSAGDNGL03) The relation workspace object is not a relation over a base dimension of AGGMAP workspace object.
ORA-32605: invalid REBUILD option
ORA-04053: error occurred when validating remote object stringstringstringstringstring
ORA-29500: NAMED keyword is invalid in CREATE JAVA CLASS
Oracle Errors 
