Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-00369: Current log of thread string not useable and
other log being cleared
- 1 Answers
- 3410 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: Attempt to open thread failed because it is necessary
to switch redo generation to another online log, but all the
other logs are being cleared or need to be archived before
they can be used.
Action: If the ALTER DATABASE CLEAR LOGFILE command is still
active then wait for it to complete. Otherwise reissue the
CLEAR command. If there are other online logs for the
thread, that are not being cleared, then archive the logs.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
LPX-00203: could not read from "~s" (error ~u)
ORA-32150: Cannot perform operation on a null timestamp
ORA-15026: disk 'string' is not an ASM disk
RMAN-08519: channel string: scanning datafilecopy string
RMAN-06064: creating datafile fno=string name=string
NNO-00267: warning: configuration database contains no data for server "string"
ORA-29303: user does not login as SYS
ORA-24142: invalid ruleset name
ORA-16736: unable to find the destination entry of standby "string" in V$ARCHIVE_DEST
QSM-02170: tables must be identical across the UNION operator
ORA-35282: (SNSYN166) The format of the AGGREGATE function is: AGGREGATE(varname USING aggmap-name [COUNTVAR intvar-name] [FORCECALC])
AMD-00152: Workspace "string" is not currently open.
Oracle Errors 
