Question

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

  • 30 March 2020
  • 6 replies
  • 933 views

Userlevel 1
Badge +2

Hello, 

I try to migrate documents from IFS 7.5 to IFS10, but during this process ( PL/SQL script ) for some documents I get Oracle error ORA-00376.

Does anyone experience this error ? 

Here is part of my log file. 

 00810) (13:31:03.791)T   Create_Document ORIGINAL: objid_=AAATRGAAGAADW+aAAM, objversion_=20200325133103
 00811) (13:31:03.797)W   ORDER_NO=315698^-NODOKUMENTY-1380180-1-A1-1
 00812) (13:31:03.797)W    ORA-00376: file 57 cannot be read at this time
ORA-01111: name for data file 57 is unknown - rename to correct file
ORA-01110: data file 57: 'C:\ORACLE\ORACLE11204\DATABASE\MISSING00057'
ORA-02063: preceding 3 lines from AGOST

Here I found some information about this error  … 

https://community.oracle.com/thread/2317124

But when I try to check information about my file 57 ( this one is connected with this error ), everything seems to be all right with it. 

IFSAPP@AGOST> select file#, status, error, tablespace_name, ts#, rfile#, bytes, blocks, name from v$datafile_header where file# = 57;
   FILE#    STATUS    ERROR    TABLESPACE_NAME    TS#    RFILE#         BYTES    BLOCKS                                 NAME
________ _________ ________ __________________ ______ _________ _____________ _________ ____________________________________
      57 ONLINE             IFSAPP_LOB              8        57    7340032000    896000 G:\ORADATA\AGOST\IFSAPP_LOB09.ORA

 

Thanks for your advices, 

Pavel 

 


6 replies

Userlevel 7

Can you run the following query (connected as sys)and share the result?

select * from v$recover_file;

 

Userlevel 1
Badge +2

yes, of course …

 

IFSAPP@AGOST> select * from v$recover_file;

no rows selected

 

when try to run command to see status of rollback, some of them are offline ( but I don’t know if it could be connected with ORA-00375 error, I just found some information on the internet to check it ) 

 

select segment_name, tablespace_name, status from dba_rollback_segs;
            SEGMENT_NAME    TABLESPACE_NAME     STATUS
________________________ __________________ __________
SYSTEM                   SYSTEM             ONLINE
_SYSSMU1_1784918585$     UNDO               ONLINE
_SYSSMU2_2760513459$     UNDO               ONLINE
_SYSSMU3_3237437755$     UNDO               ONLINE
_SYSSMU4_3000026951$     UNDO               ONLINE
_SYSSMU5_1285964568$     UNDO               ONLINE
_SYSSMU6_2373888943$     UNDO               ONLINE
_SYSSMU7_1996335245$     UNDO               ONLINE
_SYSSMU8_1143936265$     UNDO               ONLINE
_SYSSMU9_1498578474$     UNDO               ONLINE
_SYSSMU10_2353508356$    UNDO               ONLINE
_SYSSMU11_135343500$     UNDO               ONLINE
_SYSSMU12_1323025229$    UNDO               ONLINE
_SYSSMU13_4251294881$    UNDO               ONLINE
_SYSSMU14_2848013492$    UNDO               ONLINE
_SYSSMU15_3780088937$    UNDO               ONLINE
_SYSSMU16_2704955726$    UNDO               ONLINE
_SYSSMU17_2930881643$    UNDO               ONLINE
_SYSSMU18_2002457310$    UNDO               ONLINE
_SYSSMU19_2702613290$    UNDO               ONLINE
_SYSSMU20_1288927199$    UNDO               ONLINE
_SYSSMU21_4035730273$    UNDO               ONLINE
_SYSSMU22_1569279320$    UNDO               ONLINE
_SYSSMU23_2640035638$    UNDO               ONLINE
_SYSSMU24_1036915023$    UNDO               OFFLINE
_SYSSMU25_353338146$     UNDO               OFFLINE
_SYSSMU26_3637694688$    UNDO               OFFLINE
_SYSSMU27_1706357062$    UNDO               OFFLINE
_SYSSMU28_358290644$     UNDO               OFFLINE
_SYSSMU29_2237565235$    UNDO               OFFLINE
_SYSSMU30_3978007208$    UNDO               OFFLINE
_SYSSMU31_278493504$     UNDO               OFFLINE
_SYSSMU32_2664762801$    UNDO               OFFLINE
_SYSSMU33_1707933483$    UNDO               OFFLINE
_SYSSMU34_2682235617$    UNDO               OFFLINE
_SYSSMU35_2864720114$    UNDO               OFFLINE
_SYSSMU36_3266435760$    UNDO               OFFLINE
_SYSSMU37_2541390129$    UNDO               OFFLINE
_SYSSMU38_3991847361$    UNDO               OFFLINE
_SYSSMU39_3294738599$    UNDO               OFFLINE
_SYSSMU40_999717050$     UNDO               OFFLINE


41 rows selected.

 

Userlevel 7

yes, of course …

 

IFSAPP@AGOST> select * from v$recover_file;

no rows selected

 

when try to run command to see status of rollback, some of them are offline ( but I don’t know if it could be connected with ORA-00375 error, I just found some information on the internet to check it ) 

 

select segment_name, tablespace_name, status from dba_rollback_segs;
            SEGMENT_NAME    TABLESPACE_NAME     STATUS
________________________ __________________ __________
SYSTEM                   SYSTEM             ONLINE
_SYSSMU1_1784918585$     UNDO               ONLINE
_SYSSMU2_2760513459$     UNDO               ONLINE
_SYSSMU3_3237437755$     UNDO               ONLINE
_SYSSMU4_3000026951$     UNDO               ONLINE
_SYSSMU5_1285964568$     UNDO               ONLINE
_SYSSMU6_2373888943$     UNDO               ONLINE
_SYSSMU7_1996335245$     UNDO               ONLINE
_SYSSMU8_1143936265$     UNDO               ONLINE
_SYSSMU9_1498578474$     UNDO               ONLINE
_SYSSMU10_2353508356$    UNDO               ONLINE
_SYSSMU11_135343500$     UNDO               ONLINE
_SYSSMU12_1323025229$    UNDO               ONLINE
_SYSSMU13_4251294881$    UNDO               ONLINE
_SYSSMU14_2848013492$    UNDO               ONLINE
_SYSSMU15_3780088937$    UNDO               ONLINE
_SYSSMU16_2704955726$    UNDO               ONLINE
_SYSSMU17_2930881643$    UNDO               ONLINE
_SYSSMU18_2002457310$    UNDO               ONLINE
_SYSSMU19_2702613290$    UNDO               ONLINE
_SYSSMU20_1288927199$    UNDO               ONLINE
_SYSSMU21_4035730273$    UNDO               ONLINE
_SYSSMU22_1569279320$    UNDO               ONLINE
_SYSSMU23_2640035638$    UNDO               ONLINE
_SYSSMU24_1036915023$    UNDO               OFFLINE
_SYSSMU25_353338146$     UNDO               OFFLINE
_SYSSMU26_3637694688$    UNDO               OFFLINE
_SYSSMU27_1706357062$    UNDO               OFFLINE
_SYSSMU28_358290644$     UNDO               OFFLINE
_SYSSMU29_2237565235$    UNDO               OFFLINE
_SYSSMU30_3978007208$    UNDO               OFFLINE
_SYSSMU31_278493504$     UNDO               OFFLINE
_SYSSMU32_2664762801$    UNDO               OFFLINE
_SYSSMU33_1707933483$    UNDO               OFFLINE
_SYSSMU34_2682235617$    UNDO               OFFLINE
_SYSSMU35_2864720114$    UNDO               OFFLINE
_SYSSMU36_3266435760$    UNDO               OFFLINE
_SYSSMU37_2541390129$    UNDO               OFFLINE
_SYSSMU38_3991847361$    UNDO               OFFLINE
_SYSSMU39_3294738599$    UNDO               OFFLINE
_SYSSMU40_999717050$     UNDO               OFFLINE


41 rows selected.

 

Might be worth logging an LCS case so that someone can have a look at your specific db. 

Userlevel 1
Badge +2

What is very strange, Oracle wants file on disk C:\

but all datafiles are on disk G:\

 

 00812) (13:31:03.797)W    ORA-00376: file 57 cannot be read at this time
ORA-01111: name for data file 57 is unknown - rename to correct file
ORA-01110: data file 57: 'C:\ORACLE\ORACLE11204\DATABASE\MISSING00057'
ORA-02063: preceding 3 lines from AGOST

 

 

Userlevel 6
Badge +18

Can you please provide more details regarding the database reporting this error?

If it is a non-production issue, did you refresh with a standby instance?

 

You can try these steps to resolve the issue: Connect as SYS  or any SYSDBA user and issue these commands -

shutdown immediate;
startup nomount;
alter database mount database;
alter database create datafile 'C:\ORACLE\ORACLE11204\DATABASE\MISSING00057' as 'G:\ORADATA\AGOST\IFSAPP_LOB09.ORA';
alter database open;

 

I cannot fully explain why you ran into this issue but it is common to run into this error when a datafile has been added in the Production is missing in the managed Standby database.

The missing file location defaults to the ORACLE_BASE location on the database server.

 

Userlevel 6
Badge +18

Hi, Any luck with your DB issue?

Reply