Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    ORA-00376: file nn cannot be read at this time

    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    We had a problem with a disk array earlier today that made one of our file systems unavailable and kept Aleph from coming up. Once the file system access was restored we began to get Oracle error messages (in the pc_server log), such as:

    Oracle error: io_z35_write
    ORA-00376: file 46 cannot be read at this time
    ORA-01110: data file 46

    [From site:] The Oracle alert log is /exlibris/app/oracle/admin/aleph18/bdump/alert_aleph18.log

    The pertinent errors are:

    Sun Nov 26 10:05:01 2006
    KCF: write/open error block=0x31d60 online=1
    file=46 /exlibris2/oradata/aleph18/aleph18_ts2x_05.dbf
    error=27063 txt: 'SVR4 Error: 5: I/O error
    Additional information: -1
    Additional information: 8192'
    Automatic datafile offline due to write error on
    file 46: /exlibris2/oradata/aleph18/aleph18_ts2x_05.dbf

    when the array became unavailable and then

    Sun Nov 26 15:50:42 2006
    ORACLE Instance aleph18 (pid = 8) - Error 376 encountered while recovering transaction (4, 27) on object 52027.
    Sun Nov 26 15:50:42 2006
    Errors in file /exlibris/app/oracle/admin/aleph18/bdump/aleph18_smon_9198.trc:
    ORA-00376: file 46 cannot be read at this time
    ORA-01110: data file 46: '/exlibris2/oradata/aleph18/aleph18_ts2x_05.dbf'

    since then.

    The resolution was to do an Oracle 'recover datafile' and 'online datafile'--as we have been in ARCHIVELOG
    mode the entire time.

    Note: We checked the status of all data files, and the only one in RECOVER status in V$DATAFILE is

    Additional Information


    • Article last edited: 10/8/2013