WARNING:Could not set the asynch I/O limit to nnnn for SQL directo I/O. It is set to 200. (Doc ID 848859.1)

Last updated on DECEMBER 06, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.7 to 11.1.0.7 [Release 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

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms