ORACLE アラームログにORA-00204,ORA-00202, ORA-15081エラでASMのアクセスに影響を与えた

 

ORACLEデータベース によくあるエラ の解決策

プロのOracle Databaseの復旧サービスを提供
携帯番号: +86 13764045638 メール:[email protected]

適用範囲

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:([email protected] (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制定をチェックしてください。

 


Posted

in

by

Tags:

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *