| Back to Questions Page |
| |
| Question |
ORA-00313: open failed for members of log group string of
thread string |
Rank |
Answer Posted By |
|
Question Submitted By :: Guest |
|
I also faced this Question!! |
© ALL Interview .com |
| Answer | Cause: The online log cannot be opened. May not be able to
find file.
Action: See accompanying errors and make log available.
Please add more information about this Error  |
| Guest |
| |
| |
| Question |
ORA-00312: online log string thread string: 'string' |
Rank |
Answer Posted By |
|
Question Submitted By :: Guest |
|
I also faced this Question!! |
© ALL Interview .com |
| Answer | Cause: This message reports the filename for details of
another message.
Action: Other messages will accompany this message. See the
associated messages for the appropriate action to take.
Please add more information about this Error  |
| Guest |
| |
| |
| Question |
ORA-00311: cannot read header from archived log |
Rank |
Answer Posted By |
|
Question Submitted By :: Guest |
|
I also faced this Question!! |
© ALL Interview .com |
| Answer | Cause: An I/O error occurred when attempting to read the log
file header from the specified archived redo log file.
Action: Other messages will accompany this message. See the
associated messages for the appropriate action to take.
Please add more information about this Error  |
| Guest |
| |
| |
|
|
| |
| Question |
ORA-00310: archived log contains sequence string; sequence
string required |
Rank |
Answer Posted By |
|
Question Submitted By :: Guest |
|
I also faced this Question!! |
© ALL Interview .com |
| Answer | Cause: The archived log is out of sequence, probably because
it is corrupted or the wrong redo log filename was specified
Action: Specify the correct redo log file; then retry the
operation.
Please add more information about this Error  |
| Guest |
| |
| |
| Question |
ORA-00309: log belongs to wrong database |
Rank |
Answer Posted By |
|
Question Submitted By :: Guest |
|
I also faced this Question!! |
© ALL Interview .com |
| Answer | Cause: The system cannot access the archived redo log
because it belongs to another database.
Action: Specify the correct redo log file, then retry the
operation.
Please add more information about this Error  |
| Guest |
| |
| |
| Question |
ORA-00308: cannot open archived log 'string' |
Rank |
Answer Posted By |
|
Question Submitted By :: Guest |
|
I also faced this Question!! |
© ALL Interview .com |
| Answer | Cause: The system cannot access a required archived redo log
file.
Action: Check that the off line log exists, the storage
device is online, and the archived file is in the correct
location. Then attempt to continue recovery or restart the
recovery session.
Please add more information about this Error  |
| Guest |
| |
| |
| Question |
ORA-00307: requested INSTANCE_NUMBER out of range, maximum
is string |
Rank |
Answer Posted By |
|
Question Submitted By :: Guest |
|
I also faced this Question!! |
© ALL Interview .com |
| Answer | Cause: The initialization parameter INSTANCE_NUMBER
specified a number that was out of range.
Action: Change INSTANCE_NUMBER to a valid range and restart
the instance. The minimum value is one and the maximum value
is the lower of the operating system-specific maximum or the
MAXINSTANCES option specified in the CREATE DATABASE
statement. See also your operating system-specific Oracle
Please add more information about this Error  |
| Guest |
| |
| |
| Question |
ORA-00306: limit of string instances in this database |
Rank |
Answer Posted By |
|
Question Submitted By :: Guest |
|
I also faced this Question!! |
© ALL Interview .com |
| Answer | Cause: Starting this instance would exceed the maximum
number of instances allowed for this database. This message
occurs only with STARTUP shared and multiple instances.
Action: You cannot start more than the lower of a)
port-specific limit as to the number of instances b) the
number of instances specified at create-database time
Please add more information about this Error  |
| Guest |
| |
| |
| Question |
ORA-00305: log string of thread string inconsistent; belongs
to another database |
Rank |
Answer Posted By |
|
Question Submitted By :: Guest |
|
I also faced this Question!! |
© ALL Interview .com |
| Answer | Cause: The database ID in the redo log file does not match
the database ID in the controlfile. This redo log file is
not from the current database.
Action: Specify the correct redo log file, then retry the
operation.
Please add more information about this Error  |
| Guest |
| |
| |
| Question |
ORA-00304: requested INSTANCE_NUMBER is busy |
Rank |
Answer Posted By |
|
Question Submitted By :: Guest |
|
I also faced this Question!! |
© ALL Interview .com |
| Answer | Cause: An instance tried to start by using a value of the
initialization parameter INSTANCE_NUMBER that is already in use.
Action: Either a) specify another INSTANCE_NUMBER, b) shut
down the running instance with this number c) wait for
instance recovery to complete on the instance with this number.
Please add more information about this Error  |
| Guest |
| |
| |
| Question |
ORA-00303: cannot process Parallel Redo |
Rank |
Answer Posted By |
|
Question Submitted By :: Guest |
|
I also faced this Question!! |
© ALL Interview .com |
| Answer | Cause: A redo log containing Parallel Redo has been
detected. The current Oracle release cannot process this
format of redo.
Action: Use a later release that supports Parallel Redo. to
process this log.
Please add more information about this Error  |
| Guest |
| |
| |
| Question |
ORA-00302: limit of string logs exceeded |
Rank |
Answer Posted By |
|
Question Submitted By :: Guest |
|
I also faced this Question!! |
© ALL Interview .com |
| Answer | Cause: The maximum number of redo log files has been
exceeded. There is a limit, set at database creation, on the
number of redo log files (typically 16).
Action: Use the CREATE CONTROLFILE command with a larger
value for MAXLOGFILES.
Please add more information about this Error  |
| Guest |
| |
| |
| Question |
ORA-00301: error in adding log file 'string' - file cannot
be created |
Rank |
Answer Posted By |
|
Question Submitted By :: Guest |
|
I also faced this Question!! |
© ALL Interview .com |
| Answer | Cause: The creation of the redo log file failed
Action: Check: 1) there is enough storage space on the
device 2) the name of the file is valid 3) the device is
online 4) an IO error occurred Also, it is possible REUSE
was specified on the command line and a file of the
incorrect size exists. Either do not specify REUSE or use a
file of the correct size.
Please add more information about this Error  |
| Guest |
| |
| |
| Question |
ORA-00300: illegal redo log block size string specified -
exceeds limit of string |
Rank |
Answer Posted By |
|
Question Submitted By :: Guest |
|
I also faced this Question!! |
© ALL Interview .com |
| Answer | Cause: The specified block size of the redo log is greater
than the maximum block size for the operating system.
Action: Create the redo log on a device with a smaller block
size
Please add more information about this Error  |
| Guest |
| |
| |
| Question |
ORA-00299: must use file-level media recovery on data file
string |
Rank |
Answer Posted By |
|
Question Submitted By :: Guest |
|
I also faced this Question!! |
© ALL Interview .com |
| Answer | Cause: The control file does not contain an entry for this
file, so block media recovery cannot be done.
Action: Restore the data file and perform file-level media
recovery.
Please add more information about this Error  |
| Guest |
| |
| |
|
| |
|
Back to Questions Page |