ORA-00376: file x cannot be read at this time Solution

ORA-00376: file x cannot be read at this time solves the problem of data center power failure before, after restarting the database found a ORA-00376 error. Query the data file status: SQL> select file_id, online_status from dba_data_files order by 1; FILE_ID ONLINE_STATUS ---------- ----------- 1 SYSTEM 2 ONLINE 3 ONLINE 4 ONLINE 5 RECOVER 6 ONLINE 7 RECOVER 8 ONLINE 9 ONLINE 10 ONLINE 11 RECOVER 12 ONLINE 13 RECOVER 14 RECOVER 15 RECOVER 16 RECOVER file appears A large number of recover statuses, media recovery is required. SQL> select file #, status, fuzzy, checkpoint_time, checkpoint_change #, resetlogs_change #, resetlogs_time from v $ datafile_header where file # = 5; FILE # status fuzzy CHECKPOINT_TIME CHECKPOINT_CHANGE # RESETLOGS_CHANGE # RESETLOGS_TIME ---------- ------- ----- --------------- begin certificate ---------------- 5 offline yes 2013-6-19 9: 52: 38391683 940976 the current data file scn number is 3839 1683, you need to find the archive log or redo log of another height. SQL> Select sequence #, name, first_change #, next_change # from v $ archived_log; SEQUENCE # NAME FIRST_CHANGE # NEXT_CHANGE # ---------- orders ----------- ------------ 465 D: \ APP \ ARCHIVELOG \ arc00000001__0815512562.0001 36366097 36618224 466 D: \ APP \ ARCHIVELOG \ ARC0000000466_0815512562.0001 36618224 36843775 467 D: \ APP \ ARCHIVELOG \ ARC 2017000467_0815512562.0001 36843775 37065721 468 D: \ APP \ ARCHIVELOG \ Jun 37065721 37294978 469 37294978 D: \ APP \ ARCHIVELOG \ Jun 37572830 470 37572830 D: \ APP \ ARCHIVELOG \ Jun 37818186 471 D: \ APP \ ARCHIVELOG \ arc0000000471090815512562.0001 37818186 38093499 472 D: \ APP \ ARCHIVELOG \ ARC0000000472_0815512562.0001 38093499 38346397 473 D: \ APP \ ARCHIVELOG \ ARC0000000473_0815512562.0001 38346397 38381157 lucky, 38391683 is greater than 473, the largest archive log SCN, I do not need archive log help. The information required for recover is in the redo log. For example, if the data file file_id is 5 and is in the recover State, execute alter database recover datafile 5 and restore the data file in the recover State in sequence. Check whether online_status is offline again. Execute Alter database datafile 5 online. In turn, the offline data files are ONLINE. After the database is in the open state, it can be used. If the database is in the No Archive log status, the information required for recover can only be obtained from the redo log. If the redo log is overwritten, the online data file cannot be obtained, you can only think of other methods. Possible causes and solutions summary: ==================================================. tablespace or Datafile offline. b. datafile does not exist at the OS level. c. datafile locked by Backup Software. d. incorrectly set ULIMIT on UNIX. e. rollback Segment with active transactions is unavailable F. possible Other Causes.