ORA-01292: no log file has been specified for the current
LogMiner session
- 2 Answers
- 15827 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / guest
Cause: No logfile has been specified for the LogMiner session.
Action: Specify atleast one log file.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / sachin
Hi,
Actually the redo log file needs to be specified here it
may be online or archived so put the names
against "LOGFILENAME => " and go further and let me know
in case of any issues
| Is This Answer Correct ? | 0 Yes | 2 No |
ORA-22283: filename contains characters that refer to parent directory
ORA-00398: abort thread recovery due to reconfiguration
ORA-24813: cannot send or receive an unsupported LOB
TNS-12197: TNS:keyword-value resolution error
TNS-04020: CMCTL Version: number.number.number.number.number
ORA-21615: copy of an OTS (named or simple) instance failed
ORA-16145: archival for thread# string sequence# string in progress
ORA-29705: ACTIVE_INSTANCE_COUNT is string which is incompatible with the value in other instances
ORA-19002: Missing XMLSchema URL
LSX-00125: "restriction" element is improperly defined
ORA-14128: FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION
DRG-51017: unable to open storage buffer for fuzzy match candidates
Oracle Errors 
