数据库DOWN之ORA-27061: waiting for async I/Os failed

症状：数据库日志记录

Thu Oct 8 12:11:51 2009
Errors in file /oracle/admin/cpqs/bdump/cpqs_dbw0_315766.trc:
ORA-27061: waiting for async I/Os failed
IBM AIX RISC System/6000 Error: 22: Invalid argument
Thu Oct 8 12:11:51 2009
DBW0: terminating instance due to error 27061
Instance terminated by DBW0, pid = 315766

原因分析 ：

主题:	ORA-27061: waiting for async I/Os failed on IBM AIX RISC System/6000 Error: 22: Invalid argument
	文档 ID:	464768.1	类型:	PROBLEM
	Modified Date:	04-APR-2009	状态:	MODERATED

In this Document
Symptoms
Changes
Cause
Solution
References

---

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2 to 10.2.0.4
This problem can occur on any platform.

Symptoms

When starting up the instance after instance crash got error:
ORA-27061: waiting for async I/Os failed on IBM AIX RISC System/6000 Error: 22: Invalid argument.

The following messages in the alert log
-------------------------------------------------------------------
.............
Mon Oct 8 22:57:05 2007
Errors in file /dwrac/BDUMP/dwhp_p009_1941690.trc:
ORA-27061: waiting for async I/Os failed <<
IBM AIX RISC System/6000 Error: 22: Invalid argument
ORA-10388: parallel query server interrupt (failure)
Mon Oct 8 22:57:13 2007
Abort recovery for domain 0
Mon Oct 8 22:57:13 2007
Aborting crash recovery due to slave death, attempting serial crash recovery

Changes

The trace file contains:
--------------------------
Slave exiting with ORA-10388 exception

ORA-00600: internal error code, arguments: [kjccbatchstart:1], [89], [], [], [], [], [], []
Call stack:
kjccbatchstart kjbbatchstart kcllkopb kclgvlk kcbzib kcbgcur
ktbgcur kdiulk kcoubk ktprundo_intra ktprits ktprmai
kxfprdp opirip opidrv sou2o opimai_real main

ORA-00600: internal error code, arguments: [kjsmesm:svrmode], [1], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [kjccbatchstart:1], [89], [], [], [], [], [], []
Call stack:
kjsmesm kjusuc ksipgetctx ksqcmi ksqgtlctx ksqgelctx
kccocx kccbcx kcradx1 kcbdnbRedo kcbdnb ksedmp
ksfdmp kgerinv kgeasnmierr kjccbatchstart kjbbatchstart kcllkopb
kclgvlk kcbzib kcbgcur ktbgcur kdiulk kcoubk
ktprundo_intra ktprits ktprmai kxfprdp opirip opidrv
sou2o opimai_real main start

Cause

The cause of the ORA-600 and crash is to be found in the Async IO problem.Since the error is
happening in the p009 process and not DBWR.

Solution

This problem is known to affect Oracle, and here is the solution from IBM:

Ther is an emergency fix available called APAR IZ03260 lio_listio fails to update aio control blocks on
error.

Local Fix:

Users affected:

* systems running aix 5.3 with the bos.rte.aio fileset at the 5.3.0.60 or 5.3.0.61 level.
* this problem is known to affect oracle.

Problem description:

When the maximum requests (maxreqs) is exceeded, lio_listio will update the control blocks, but may not return an error to indicate that some i/os were not started. this results in an unexpected einval from aio_nwait later when these i/os are waited for.

* errors similar to the following may be logged by oracle:
* ora-27061: waiting for async i/os failed
* ibm aix risc system/6000 error: 22: invalid argument

Recommendation:

* increase the max limit for aio requests using the chdev command.
* install apar iz03260.

Problem Conclusion:

++ lio_listio should return proper error codes on failures.[@more@]

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/9225895/viewspace-1027653/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/9225895/viewspace-1027653/