怎么解决数据库alert报错ORA-00202

本篇内容主要讲解“怎么解决数据库alert报错ORA-00202”，感兴趣的朋友不妨来看看。本文介绍的方法操作简单快捷，实用性强。下面就让小编来带大家学习“怎么解决数据库alert报错ORA-00202”吧!思路分析：1、发现数据库宕机，检查alert日志发现如下出现控制文件：I/O错误Thu Apr 11 06:40:14 2019
WARNING: Read Failed. group:2 disk:1 AU:675 offset:16384 size:16384
WARNING: failed to read mirror side 1 of virtual extent 0 logical extent 0 of file 260 in group [2.3852408873] from disk DATA_0001 allocation unit 675 reason error; if possible, will try another mirror side
Errors in file /u01/app/oracle/diag/rdbms/jsswgsjk/jsswgsjk1/trace/jsswgsjk1_ckpt_93628.trc:
ORA-00202: control file: ‘+DATA/jsswgsjk/controlfile/current.260.998936297’
ORA-15081: failed to submit an I/O operation to a disk
ORA-27072: File I/O error
Linux-x86_64 Error: 5: Input/output error
Additional information: 4
Additional information: 1382432
Additional information: -1
Thu Apr 11 06:40:15 2019
WARNING: Read Failed. group:2 disk:1 AU:675 offset:65536 免费主机域名size:163842、检查ASM日志——-发生磁盘超时，开始dimountOCRThu Apr 11 06:39:29 2019NOTE: process _b000_+asm1 (31654636) initiating offline of disk 0.3671375779 (OCR_0000) with mask 0x7e in group 3NOTE: process _b000_+asm1 (31654636) initiating offline of disk 1.3671375780 (OCR_0001) with mask 0x7e in group 3NOTE: process _b000_+asm1 (31654636) initiating offline of disk 2.3671375781 (OCR_0002) with mask 0x7e in group 3NOTE: checking PST: grp = 3GMON checking disk modes for group 3 at 13 for pid 67, osid 31654636ERROR: no read quorum in group: required 2, found 0 disksNOTE: checking PST for grp 3 done.NOTE: initiating PST update: grp = 3, dsk = 0/0xdad4bfa3, mask = 0x6a, op = clearNOTE: initiating PST update: grp = 3, dsk = 1/0xdad4bfa4, mask = 0x6a, op = clearNOTE: initiating PST update: grp = 3, dsk = 2/0xdad4bfa5, mask = 0x6a, op = clearGMON updating disk modes for group 3 at 14 for pid 67, osid 31654636ERROR: no read quorum in group: required 2, found 0 disks
Thu Apr 11 06:39:29 2019解决方案：1、综合以上信息分析，故障分析总结如下：Oracle RAC ASM管理磁盘组有一种特有的心跳磁盘监控’ASM PST heartbeat’，这个监控是在oracle 11.2.0.3之后出现，系统默认设至是15s，到12.1.0.2之后oracle把默认值改为了120s。这个PST heartbeat：往往发生在IO闪断/繁忙/CPU繁忙时，PST检测到同步延迟超过”_asm_hbeatiowait”值时，会通知ORACLE ASM INSTANCE dismount disk group，造成ASM instance disk group offline。一般Normal Redundancy或者High Redundancy策略下，超过半数的disk group offline就会造成Rack脑裂。我们任何的升级在链路切换中，PP一般会hold住 IO 15秒钟左右再恢复，很大可能性会引起上述timeout问题，在升级之前强烈建议更改此参数值到120。具体的检查这个参数的办法如下，修改为120s后，为确保设置生效，需要重启CRS服务。2、检查参数 “_asm_hbeatiowait”的值：（检查为：15）select ksppinm as “hidden parameter”, ksppstvl as “value” from x$ksppi join x$ksppcvusing (indx)where ksppinm like ‘_%’ escape ” and ksppinm like ‘%asm_hb%’order by ksppinm;3、修改方案，在ASM实例下调整alter system set “_asm_hbeatio免费主机域名wait”=120 scope=spfile;注意重启ASM或者CRS到此，相信大家对“怎么解决数据库alert报错ORA-00202”有了更深的了解，不妨来实际操作一番吧！这里是云技术网站，更多相关内容可以进入相关频道进行查询，关注我们，继续学习！

相关推荐: 怎么处理ORACLE悬疑分布式事务问题

这篇文章主要讲解了“怎么处理ORACLE悬疑分布式事务问题”，文中的讲解内容简单清晰，易于学习与理解，下面请大家跟着小编的思路慢慢深入，一起来研究和学习“怎么处理ORACLE悬疑分布式事务问题”吧！当需要在多个Oracle数据库之间进行数据一致性操作时，就会用…