If the Alert Log contains the following information:
* ** Session ID: (538.48) 08:41:30. 649
Warning: cocould not lower the asynch I/O limit to 224 for SQL direct I/O. It is set to-1
Warning: cocould not lower the asynch I/O limit to 192 for SQL direct I/O. It is set to-1
Warning: cocould not lower the asynch I/O limit to 224 for SQL direct I/O. It is set to-1
Warning: cocould not lower the asynch I/O limit to 192 for SQL direct I/O. It is set to-1
Warning: cocould not lower the asynch I/O limit to 160 for SQL direct I/O. It is set to-1
Cause:
This seems due to bug 9772888 10.2.0.5 RDBMS 10.2.0.5 buffer cache PRODID-5 PORTID-23 Abstract: Warning: cocould not lower the asynch I/O limit to 160 for SQL direct I/O. It is Se
Same behavior appears and on the same platform 10.2.0.5
Two versions affected by this bug:
10.2.0.5
11.2.0.1
The following versions have been fixed:
12.1 (future release)
11.2.0.2 (server patch set)
10.2.0.5.2 Patch Set Update
10.2.0.5 patch 1 on Windows Platforms
Previously, the database was upgraded to 10.2.0.5. You have not encountered this bug. However, some people have already met in the Forum. Pay attention to it.
Bytes ---------------------------------------------------------------------------------------------------
Blog: http://blog.csdn.net/tianlesoftware
Online Resources: http://tianlesoftware.download.csdn.net
Video: http://blog.csdn.net/tianlesoftware/archive/2009/11/27/4886500.aspx
Dba1 group: 62697716 (full); dba2 group: 62697977 (full) dba3 group: 62697850 (full)
Super DBA group: 63306533 (full); dba4 group: 83829929 dba5 group: 142216823
Chat group: 40132017 chat 2 group: 69087192
-- Add the group to describe the relationship between Oracle tablespace and data files in the remarks section. Otherwise, the application is rejected.