SQL> startup
ORACLE instance started.Total System Global Area 1227851088 bytes
Fixed Size 742736 bytes
Variable Size 805306368 bytes
Database Buffers 419430400 bytes
Redo Buffers 2371584 bytes
Database mounted.
ORA-27061: skgfospo: waiting for async I/Os failed
IBM AIX RISC System/6000 Error: 22: Invalid argument
ORA-27061: skgfospo: waiting for async I/Os failed
IBM AIX RISC System/6000 Error: 22: Invalid argument
请问哪位xdjm碰到过上面这种问题?
我重启了机器,还是这样。
ORACLE instance started.Total System Global Area 1227851088 bytes
Fixed Size 742736 bytes
Variable Size 805306368 bytes
Database Buffers 419430400 bytes
Redo Buffers 2371584 bytes
Database mounted.
ORA-27061: skgfospo: waiting for async I/Os failed
IBM AIX RISC System/6000 Error: 22: Invalid argument
ORA-27061: skgfospo: waiting for async I/Os failed
IBM AIX RISC System/6000 Error: 22: Invalid argument
请问哪位xdjm碰到过上面这种问题?
我重启了机器,还是这样。
解决方案 »
- 请高手指点下 oracle 的 function 不太会用...
- 如何把Oracle还原到出事状态啊?
- 一行变多行
- 使用sqlplus login是oracle报2165的错误,请各位多多指点!
- 怎么改这个SQL语句
- 请教一个很简单的问题,先谢了!!!
- 奇怪的sql错误 ora-03113 ,不明白为什么,只能请教高手咯
- 各位大侠,请问有没有编写PL/SQL脚本程序好用一点的工具?急~~~
- PL/SQL CTRL 鼠标左键 超链接跳转这个功能如何设置
- shell有个oracle方面的小需求。
- 安装oracle10g时出现的问题
- ORA-0000: normal, successful completion
Doc ID: 452866.1 Solution
--------------------------------------------------Increase the max limit for AIO requests (maxreqs) using the chdev command.
The command to make the change permanent after reboot is:
chdev -l aio0 -a maxreqs=<value>The command to make the change effective dynamically is:
aioo -o maxreqs=<value>To check current Setting for maximum requests (maxreqs) :
lsattr -El aio0
Oracle Server - Enterprise Edition - Version: 9.2.0.8
This problem can occur on any platform.Symptoms
-- Problem Statement:
Periodical database crashes with the following errors:
ORA-27061: skgfospo: waiting for async I/Os failed
IBM AIX RISC System/6000 Error: 22: Invalid argumentCause
Oracle is waiting for an async. I/O to complete. aiowait() is the operating
function on AIX to handle this things and it did not return the requested data
in an appropriate time to complete the I/O. The problem is always encountered by the DBWR processes.
Solution
As a workaround, DBWR IO slaves can be increased to handle the IO workload. However, this is an issue that need to get addressed to the hardware vendor (IBM) to check driver and I/O system.-- To implement the workaround, please execute the following steps::
sql> alter system set DBWR_IO_SLAVES = 4 scope=spfile;
sql> shutdown immediate
sql> startup
.
.
.
sql>recover
.
sql>alter database open;之后再把该实例重启,就没有该问题了。