ORA-01115 ORA-01110 ORA-27091 ORA-27072 on AIX 5L

今天遇到錯誤

ORA-01115: IO error reading block from file 11 (block # 1024771)
ORA-01110: data file 11: '/oradata/ufida/NNC_DATA03_02.dbf'
ORA-27091: unable to queue I/O
ORA-27072: File I/O error
IBM AIX RISC System/6000 Error: 5: I/O error
Additional information: 3

 

然後檢視日誌並沒有錯誤記錄，同時找出這個塊的所在的表，進行了全表掃描，為發現錯誤，同時進行了DBV也未發現損壞的塊。

然後進入METALINK找到如下文章：

 

 

ORA-01115 ORA-01110 ORA-27091 ORA-27072 Error: 5: I/O error [ID 559697.1]修改時間:2011-11-18型別:PROBLEM狀態:PUBLISHED優先順序:2
註釋 (0)

 

In this Document
  Symptoms
  Changes
  Cause
  Solution
  References
Applies to:Oracle Server - Enterprise Edition - Version: 9.2.0.8and later   [Release: 9.2 and later ]
IBM AIX on POWER Systems (64-bit)
***Checked for relevance on 16-Feb-2011***

IBM AIX Based Systems (64-bit)SymptomsAfter patching the OS with Patch IBM Technology Level 6 (5300-06) or Level 7 (5300-07), the application log started reporting the following errors:

ORA-01115: IO error reading block from file (block # )
ORA-01110: data file :
ORA-27091: skgfqio: unable to queue I/O
ORA-27072: skgfdisp: I/O error
IBM AIX RISC System/6000 Error: 5: I/O error

- The errors are not reported in the alert log file.
- Running dbv against datafiles from the error messages shows no errors.
- All the mandatory OS patches are applied.
- Oracle patch for Bug 5496862- IO READING PROBLEMS AFTER INSTALLING IBM TECHNOLOGY LEVEL 5 (5300-05) was installed before patching the OS.

ChangesPatch IBM Technology Level 6 (5300-06) or higher was applied to the OS.CauseThe value of maxreqs (4096) was too low. This asynchronous I/O parameter specifies the maximum number of asynchronous I/O requests that can be outstanding at any one time and has as default value 4096.SolutionIncrease maxreqs to a value greater than or equal to 8192.Steps:
1. run aioo -a command to double check current setting for aio0 device
2. run aioo -o maxreqs= to set maxreqs dynamically
3. chdev -l aio0 -a maxreqs= -P to set the value of maxreqs permanently for next reboot
4. run aioo -a to confirm change
5. restart oracle

NOTE: Values that fixed the errors: 8192, 16384 or 32768.

應該就是這個BUG引起的然後檢視了Bug 5496862，這個BUG在10.2.0.3中已經修復，而我們的資料庫是10.2.0.4，所以不存在這個問題。