Beruflich Dokumente
Kultur Dokumente
To consolidate the common reasons & solutions for the ORA-376 error.
ORA-376
=======
An ORA-376 occurs when Oracle knows a datafile, but Oracle cannot read it.
Error Explanation:
-----------------
Cause: attempting to read from a file that is not readable. Most likely
the file is offline.
As mentioned in the error text, the common reason for this error is due to
Oracle failing to read a specific datafile. This error will usually be
accompanied by ORA-1110, which will give the name of the file that could
not be read by Oracle.
For example:
In this case, test.dbf is the name of the datafile that Oracle is failing to
read.
- Use the following query to find out the status of the tablespaces:
- Use the following query to find out the status of the datafiles.
For example:
In this case, you can drop the datafile and recreate the tablespace.
But, this is feasible for non-system and non-rollback tablespaces only.
The following error might result, if the ulimit parameter is not set properly.
This is possible especially in Oracle Parallel Server (OPS) instances, where
the node switch might happen.
For Example:
The problem is that on the new node the filesize limit is lower than it used to
be on the older node and lower than the datafile size.
$ ulimit -f <number>
In this case the solution would depend on whether the database was last
cleanly shut down or not.
F. Some other cases where the error ORA-376 was resolved include:
****************************************************************
Solution:
Again note the sequence number. Ignore the suggested logfile name.
The name will appear in the form of an archived log, but this is really
the name of the online redolog not yet archived.
If the lowest sequence number from the query results is the same as the
sequence number Oracle requires to recover database, then database can
be recovered.
Simply copy the exact path and filename from the member column as the
filename required by the RECOVER DATABASE command.
The Database in archive log mode was shutdown abort before the server
was rebooted.
SQL>shutdown immediate;
- Edit the init<SID>.ora file and remove or comment out the problem
rollback segment from the list of rollback segments in the
ROLLBACK_SEGMENTS parameter.
- Find out which files need recovery by running the following statement:
- Find out which rollback segments are offline by running the following
statement:
- Edit the init<SID>ora file and add or uncomment the problem rollback
segment back to the list of rollback segments in the ROLLBACK_SEGMENTS
parameter.
- Startup the database.