ORA-01292: no log file has been specified for the current
LogMiner session
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-09987: unable to attach to SGA in READ-ONLY mode
ORA-14186: number of sub-partitions of LOCAL index must equal that of the underlying table
TNS-00558: Entrust login failed
DRG-11606: URL store: access to string timed out waiting for client request
KUP-03009: OCI error getting column name.
ORA-01907: TABLESPACE keyword expected
TNS-02525: encryption/crypto-checksumming: self test failed
ORA-01941: SEQUENCE keyword expected
PCC-00010: Statement out of place at line number in file string
ORA-07511: sscggtl: $enq unexpected return for master termination lock
ORA-02166: ARCHIVELOG and NOARCHIVELOG specified
ORA-29848: error occurred in the execution of ODCIINDEXMERGEPARTITION routine