Email: service@parnassusdata.com 7 x 24 online support!

    You are here

    • You are here:
    • Home > Blogs > PDSERVICE's blog > ORACLE警告日志报ORA-00204,ORA-00202, ORA-15081错误影响ASM的访问 ORA-15081: 无法将 I/O 操作提交到磁盘

ORACLE警告日志报ORA-00204,ORA-00202, ORA-15081错误影响ASM的访问 ORA-15081: 无法将 I/O 操作提交到磁盘

ORACLE警告日志报ORA-00204,ORA-00202, ORA-15081错误影响ASM的访问 ORA-15081: 无法将 I/O 操作提交到磁盘

如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复!

诗檀软件专业数据库修复团队

服务热线 : 13764045638 QQ号:47079569 邮箱:service@parnassusdata.com

 

ORA-15081: 无法将 I/O 操作提交到磁盘

ORA-00202: 控制文件: ''''

ORA-00204: 读取控制文件时出错 (块 , # 块 )

 

 

适用于

Oracle数据库 – 企业版 – 10.1.0.2 到11.2.0.3 版本[Release 10.1 to 11.2]
本文档内容适用于各个平台I

症状

RAC – 2 node – 11.2.0.3.0 (asm) – 11.2.0.3.0 (db) – Linux x86-64 (RHEL5)

远程连接SQL*Plus和访问数据库时报下面的错误:Getting the below error when connected to SQL*Plus remotely and accessing the database:

$sqlplus

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 – 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options

SQL> select name from v$database;
select name from v$database
*
ERROR at line 1:
ORA-00204: error in reading (block 1, # blocks 1) of control file
ORA-00202: control file: ‘+DATA/database2/control01.ctl’
ORA-15081: failed to submit an I/O operation to a disk

11.2.0.3.0版本 RAC 数据库实例的警告日志里报下面错误:

In the  alert_database2.log:

Fri Jan 25 10:07:46 2013
Errors in file /oracle/app/oracle/diag/rdbms/database/database2/trace/database2_ora_11419.trc:
ORA-15025: could not open disk “/dev/mapper/asm5”
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 3
Errors in file /oracle/app/oracle/diag/rdbms/database/database2/trace/database2_ora_11419.trc:
ORA-15025: could not open disk “/dev/mapper/asm5”
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 3
WARNING: failed to read mirror side 1 of virtual extent 0 logical extent 0 of file 256 in group [1.3282045569] from disk DATA_05  allocation unit 22 reason error; if possible, will try another mirror side
Errors in file /oracle/app/oracle/diag/rdbms/database/database2/trace/database2_ora_11419.trc:
ORA-00202: control file: ‘+DATA/database2/control01.ctl’
ORA-15081: failed to submit an I/O operation to a disk
Fri Jan 25 10:12:02 2013

Sat Jan 26 05:15:58 2013
Errors in file /oracle/app/oracle/diag/rdbms/database/database2/trace/database2_ora_4891.trc:
ORA-15025: could not open disk “/dev/mapper/asm5”
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 3
Errors in file /oracle/app/oracle/diag/rdbms/database/database2/trace/database2_ora_4891.trc:
ORA-15025: could not open disk “/dev/mapper/asm5”
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 3
WARNING: failed to read mirror side 1 of virtual extent 0 logical extent 0 of file 256 in group [1.3282045569] from disk DATA_05  allocation unit 22 reason error; if possible, will try another mirror side
Errors in file /oracle/app/oracle/diag/rdbms/database/database2/trace/database2_ora_4891.trc:
ORA-00202: control file: ‘+DATA/database2/control01.ctl’
ORA-15081: failed to submit an I/O operation to a disk
Sat Jan 26 05:20:21 2013
Shutting down instance (immediate)

***********************************************************************

In the database2_ora_11419.trc:

*** 2013-01-25 10:07:46.040
*** SESSION ID:(620.9) 2013-01-25 10:07:46.040
*** CLIENT ID:() 2013-01-25 10:07:46.040
*** SERVICE NAME:(database2) 2013-01-25 10:07:46.040
*** MODULE NAME:(sqlplus@dbnode02.com (TNS) 2013-01-25 10:07:46.040
*** ACTION NAME:() 2013-01-25 10:07:46.040

WARNING: failed to open a disk[/dev/mapper/asm5]
ORA-15025: could not open disk “/dev/mapper/asm5”
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 3
kfk_debug_get_user_groups: uid:509, euid:503, gid:504, egid:507
WARNING: failed to open a disk[/dev/mapper/asm5]
ORA-15025: could not open disk “/dev/mapper/asm5”
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 3
kfk_debug_get_user_groups: uid:509, euid:503, gid:504, egid:507
WARNING: disk locally closed resulting in I/O error
WARNING: Read Failed. group:1 disk:4 AU:22 offset:16384 size:16384
path:Unknown disk
incarnation:0xec40fa7f synchronous result:’I/O error’
subsys:Unknown library iop:0x7f5dd1003000 bufp:0x7f5dd111ae00 osderr:0x0 osderr1:0x0
WARNING: failed to read mirror side 1 of virtual extent 0 logical extent 0 of file 256 in group [1.3282045569] from disk DATA_05  allocation unit 22 reason error; if possible, will try another mirror side

*************************************************************

原因

在每个节点上的ASM软件所有者具有适当的主要用户组,ASM OSASM,ASM OSDBA,ASM OSPER和数据库OSDBA组分配给他的。
ASM磁盘/设备设置了正确的权限和所有权。
此外,对于GRID/ ASM和数据库Oracle可执行适当的正确组设置,包括在$ GRID/ ASM HOME和$ HOME RDBMS同时设置“setasmgidwrap”。
然而,当cluvfy已运行时遇到以下错误:

Run cluvfy and see if same error will be reported:
./runcluvfy.sh stage -pre crsinst -n <node1>,<node2> -verbose

grid$ ./runcluvfy.sh stage -pre crsinst -n dbnode02 -verbose

In the runcluvfy.log:

Checking all nodes to make sure that search entry is “dbnode02.com dbnode02.net” as found on node “dbnode02”
All nodes of the cluster have same value for ‘search’
Checking DNS response time for an unreachable node
Node Name                             Status
————————————  ————————
dbnode02                            failed
dbnode01                            failed
PRVF-5636 : The DNS response time for an unreachable node exceeded “15000” ms on following nodes: dbnode02   ————–>  HERE

File “/etc/resolv.conf” is not consistent across nodes

Checking DNS response time for an unreachable node
Node Name                             Status
————————————  ————————
dbnode02                            failed
PRVF-5636 : The DNS response time for an unreachable node exceeded “15000” ms on following nodes: dbnode02  ————–>  HERE

File “/etc/resolv.conf” is not consistent across nodes

*************************************************************************

解决方案

系统/网络管理员需要找出为什么需要这么长时间,并修复它。

这可能是一个因素。因此这个PRVF-5636错误需要用NSLOOKUP检查,并查看文件/etc/resolv.conf中,在RAC环境中的每个节点上进行检查。通常情况下,通过网络团队检查DNS设置。虽然它可能会出现没有到没有直接关系“权限被拒绝”的错误,你应该检查resolve.conf和DNS设置。