Permissões de ntfs nessa pasta como estão ? Parece que a base não consegue escrever no disco
OSD-04002: unable to open file O/S-Error: (OS 1392) The file or directory is corrupted and unreadable. Unable to create archive log file 'E:\BDEDUCAR\ARCHIVELOG\2017_ 04_11\O1_MF_1_421421_%U_.ARC' ORA-19816: WARNING: Files may exist in db_recovery_file_dest that are not known to database. ORA-27040: file create error, unable to create file OSD-04002: unable to open file O/S-Error: (OS 1392) The file or directory is corrupted and unreadable. On 13 April 2017 at 08:43, alisson...@yahoo.com.br [oracle_br] < oracle_br@yahoogrupos.com.br> wrote: > > > Bom dia a todos, > > > começou a apresentar erros no banco aqui , > > > Estou com a versão Oracle Database 11g Enterprise Edition Release > 11.2.0.4.0 - 64bit Product , com todos os pacth atualizados. > > Uso Windows Server 2012 R2 > > > Fiz o procedimento sugerido Catalog Recovery area, mas o erro persiste > depois de algum tempo. > > > Alguém pode me ajudar nesse processo ? me dizendo se já passou por isso ? > > > Grato. > > > > > ORA-19816: WARNING: Files may exist in db_recovery_file_dest that are not > known to database. > > ORA-27040: file create error, unable to create file > > OSD-04002: unable to open file > > O/S-Error: (OS 1392) The file or directory is corrupted and unreadable. > > > *** 2017-04-11 22:18:23.726 > > Unable to create archive log file 'E:\BDEDUCAR\ARCHIVELOG\2017_ > 04_11\O1_MF_1_421421_%U_.ARC' > > ORA-19816: WARNING: Files may exist in db_recovery_file_dest that are not > known to database. > > ORA-27040: file create error, unable to create file > > OSD-04002: unable to open file > > O/S-Error: (OS 1392) The file or directory is corrupted and unreadable. > > ************************************************************* > > WARNING: A file of type ARCHIVED LOG may exist in > > db_recovery_file_dest that is not known to the database. > > Use the RMAN command CATALOG RECOVERY AREA to re-catalog > > any such files. If files cannot be cataloged, then manually > > delete them using OS command. This is most likely the > > result of a crash during file creation. > > > > > >