删除文件，实例宕机？是的，ora-凯发app官方网站

arc2 (pid:2324): archived log entry 5 added for t-1.s-18 id 0x605479f8 lad:1
2021-11-12 12:20:39.524000 -08:00
thread 1 cannot allocate new log, sequence 20
checkpoint not complete
current log# 1 seq# 19 mem# 0: /u01/app/oracle/oradata/orcl/redo01.log
2021-11-12 12:20:41.988000 -08:00
errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ckpt_2266.trc:
ora-63999: data file suffered media failure
ora-01116: error in opening database file 7
ora-01110: data file 7: '/u01/app/oracle/oradata/orcl/users01.dbf'
ora-27041: unable to open file
linux-x86_64 error: 2: no such file or directory
additional information: 3
errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ckpt_2266.trc:
ora-63999: data file suffered media failure
ora-01116: error in opening database file 7
ora-01110: data file 7: '/u01/app/oracle/oradata/orcl/users01.dbf'
ora-27041: unable to open file
linux-x86_64 error: 2: no such file or directory
additional information: 3
errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ckpt_2266.trc (incident=16961):
ora-63999 [] [] [] [] [] [] [] [] [] [] [] []
incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_16961/orcl_ckpt_2266_i16961.trc
errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_mz00_2781.trc:
ora-01110: data file 7: '/u01/app/oracle/oradata/orcl/users01.dbf'
ora-01565: error in identifying file '/u01/app/oracle/oradata/orcl/users01.dbf'
ora-27037: unable to obtain file status
linux-x86_64 error: 2: no such file or directory
additional information: 7
2021-11-12 12:20:43.451000 -08:00
user (ospid: 2266): terminating the instance due to ora error 63999
system state dump requested by (instance=1, osid=2266 (ckpt)), summary=[abnormal instance termination].
system state dumped to trace file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_diag_2239.trc
dumping diagnostic data in directory=[cdmp_20211112122043], requested by (instance=1, osid=2266 (ckpt)), summary=[abnormal instance termination].
2021-11-12 12:20:45.541000 -08:00
instance terminated by user, pid = 2266

这太不健壮了，所以还是让数据库容错能力恢复到原先吧

alter system set "_datafile_write_errors_crash_instance"=false;

这样的话，如果有个别文件出现问题，只在告警日志中报错，不至于整个数据库无法访问。
所有生产库都应该这样设置。

阅读(780) | 评论(0) | 转发(0) |

上一篇：oracle文件名中含有tab字符，如何改名？

下一篇：row cache object child latch map

给主人留下些什么吧！~~

| | | | |

感谢所有关心和支持过chinaunix的朋友们