暂无图片
ORACLE自动down掉,都是下边类似的IO错误。但是但是每天的IO报错具体信息都不一样
我来答
分享
伤城
2021-04-29
ORACLE自动down掉,都是下边类似的IO错误。但是但是每天的IO报错具体信息都不一样
暂无图片 5M

Thu Apr 29 11:07:37 2021
Errors in file E:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_lgwr_1132.trc:
ORA-00345: redo log write error block 7021 count 6
ORA-00312: online log 3 thread 1: ‘E:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO03.LOG’
ORA-27070: async read/write failed
OSD-04016: 异步 I/O 请求排队时出错。
O/S-Error: (OS 1117) 由于 I/O 设备错误,无法运行此项请求。
Errors in file E:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_lgwr_1132.trc:
ORA-00340: IO error processing online log 3 of thread 1
ORA-00345: redo log write error block 7021 count 6
ORA-00312: online log 3 thread 1: ‘E:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO03.LOG’
ORA-27070: async read/write failed
OSD-04016: 异步 I/O 请求排队时出错。
O/S-Error: (OS 1117) 由于 I/O 设备错误,无法运行此项请求。
Thu Apr 29 11:07:37 2021
System state dump requested by (instance=1, osid=1132 (LGWR)), summary=[abnormal instance termination].
System State dumped to trace file E:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_diag_14000_20210429110737.trc
LGWR (ospid: 1132): terminating the instance due to error 340
Thu Apr 29 11:07:38 2021
opiodr aborting process unknown ospid (11888) as a result of ORA-1092
Thu Apr 29 11:07:38 2021
ORA-1092 : opitsk aborting process
Thu Apr 29 11:07:38 2021
opiodr aborting process unknown ospid (1484) as a result of ORA-1092
Thu Apr 29 11:07:38 2021
ORA-1092 : opitsk aborting process

每天中午的时候会自己down机,下边是对应的trc文件。

*** 2021-04-29 10:55:15.695
Warning: log write elapsed time 1167ms, size 1031KB

*** 2021-04-29 10:55:16.222
Warning: log write elapsed time 526ms, size 3648KB

*** 2021-04-29 10:55:18.741
Warning: log write elapsed time 1582ms, size 141KB

*** 2021-04-29 10:55:22.383
Warning: log write elapsed time 534ms, size 1031KB

*** 2021-04-29 11:07:37.338
DDE rules only execution for: ORA 312
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: ‘DB_STRUCTURE_INTEGRITY_CHECK’ (Async) -----
Successfully dispatched
----- END DDE Action: ‘DB_STRUCTURE_INTEGRITY_CHECK’ (SUCCESS, 0 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----

*** 2021-04-29 11:07:37.339
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=2, mask=0x0)
----- Error Stack Dump -----
ORA-00345: redo log write error block 7021 count 6
ORA-00312: online log 3 thread 1: ‘E:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO03.LOG’
ORA-27070: async read/write failed
OSD-04016: 异步 I/O 请求排队时出错。
O/S-Error: (OS 1117) 由于 I/O 设备错误,无法运行此项请求。
----- SQL Statement (None) -----
Current SQL information unavailable - no cursor.

*** 2021-04-29 10:55:22.383
Warning: log write elapsed time 534ms, size 1031KB

*** 2021-04-29 11:07:37.338
DDE rules only execution for: ORA 312
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
Executing SYNC actions
----- START DDE Action: ‘DB_STRUCTURE_INTEGRITY_CHECK’ (Async) -----
Successfully dispatched
----- END DDE Action: ‘DB_STRUCTURE_INTEGRITY_CHECK’ (SUCCESS, 0 csec) -----
Executing ASYNC actions
----- END DDE Actions Dump (total 0 csec) -----

*** 2021-04-29 11:07:37.339
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=2, mask=0x0)
----- Error Stack Dump -----
ORA-00345: redo log write error block 7021 count 6
ORA-00312: online log 3 thread 1: ‘E:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO03.LOG’
ORA-27070: async read/write failed
OSD-04016: 异步 I/O 请求排队时出错。
O/S-Error: (OS 1117) 由于 I/O 设备错误,无法运行此项请求。
----- SQL Statement (None) -----
Current SQL information unavailable - no cursor.

我来答
添加附件
收藏
分享
问题补充
8条回答
默认
最新
伤城
上传附件:orcl_lgwr_1132(1).trc
暂无图片 评论
暂无图片 有用 0
伤城
上传附件:alert_orcl.log
暂无图片 评论
暂无图片 有用 0
伤城
上传附件:orcl_ckpt_9748.trc
暂无图片 评论
暂无图片 有用 0
章芋文

看下系统日志,是不是存储除了问题?

暂无图片 评论
暂无图片 有用 0
伤城

windows服务器,这个怎么看是否不是存储出了问题啊?

如果要是物理的坏块,是不是应该每次报错是一个块号啊?但是目前每次报错的信息都不一样,但是都是IO方面的报错

暂无图片 评论
暂无图片 有用 0
章芋文

Windows可以看:事件查看器

暂无图片 评论
暂无图片 有用 0
侯志清

disk_asynch_io = FALSE

设置这个参数,再观察一段时间

暂无图片 评论
暂无图片 有用 0
cqiwen

看样子可能是磁盘有坏块或者线路有问题。你说是固定时间的问题,那就要看看那个时间点有没有什么特别的操作,或者存储线路是否有什么切换的动作呢?

暂无图片 评论
暂无图片 有用 0
回答交流
提交
问题信息
请登录之后查看
附件列表
请登录之后查看
邀请回答
暂无人订阅该标签,敬请期待~~
暂无图片墨值悬赏