not set asynch I/O limit to nnnn for SQL directo I/O.It is set to 200_848859.1

rongshiyuan發表於2014-07-01
MITSQL

In this Document
  Symptoms
  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: 11.1.0.7 to 11.1.0.7 - Release: 11.1 to 11.1
Information in this document applies to any platform.
***Checked for relevance on 01-Nov-2011***

SYMPTOMS

After upgrading the database to 11.1.0.7 many trace files are generated with the following warning:

*** SERVICE NAME:(SYS$USERS) 2009-06-17 14:49:12.974 
*** MODULE NAME:(JDBC Thin Client) 2009-06-17 14:49:12.974 
*** ACTION NAME:() 2009-06-17 14:49:12.974 
WARNING:Could not set the asynch I/O limit to nnn for SQL direct I/O. It is set to 200.

Where nnnn is any number greater than 200.

Different module client calls on the database trigger it.

Checking the AIO configuration of the database we can see that the AIO is enabled :
i.e:
disk_asynch_io =TRUE

CAUSE

This is an oracle issue registered as bug 7641350

SOLUTION

1) Apply Patch 7641350 when bug is fixed

Or


2) Upgrade to 11gR2 when available 

Or 

3) Schedule an OS job to delete those trace files. 
Trace files warning messages are harmless and can be ignored. 

REFERENCES

BUG:7641350 - SINCE UPGRADED TO 11.1.0.7 GET WARNING MESSAGES WARNING:COULD NOT SET THE ASYNCH

來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/17252115/viewspace-1200680/，如需轉載，請註明出處，否則將追究法律責任。

相關文章