ORA-01292: no log file has been specified for the current
LogMiner session
- 2 Answers
- 15807 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 |
NNC-00421: invalid modification directive string, must be between string and string
RMAN-20298: DBMS_RCVCAT package not compatible with the recovery catalog
ORA-30653: reject limit reached
ORA-16506: out of memory
TNS-00206: Status Information for Interchange string:
RMAN-06211: ==========================
LSX-00213: only ~1d occurrences of particle "~2S", minimum is ~3d
ORA-19568: a device is already allocated to this session
ORA-29707: inconsistent value string for initialization parameter string with other instances
ORA-02330: datatype specification not allowed
ORA-07255: spini: cannot set up signal handler.
ORA-24776: cannot start a new transaction
Oracle Errors 
