Recently to the database to do patrol, always found warning:aiowait timed out 1 times error, the following alert content:
Thread 1 cannot allocate new log, sequence 52198
Private Strand Flush Not complete
Current log# 5 seq# 52197 mem# 0:/oradb/adc/sysfile/redo05.log
Thread 1 advanced to log sequence 52198 (LGWR switch)
Current log# 6 seq# 52198 mem# 0:/oradb/adc/sysfile/redo06.log
Thu APR 14 05:01:29 2016
Warning:aiowait timed out 1 times
Thu APR 14 05:02:03 2016
Warning:aiowait timed out 1 times
Thu APR 14 05:02:45 2016
Warning:aiowait timed out 1 times
Thu APR 14 05:03:16 2016
MINACT-SCN:USEG Scan erroring out with error e:12751
Thu APR 14 05:03:35 2016
Warning:aiowait timed out 1 times
Thu APR 14 05:05:16 2016
Warning:aiowait timed out 1 times
Thu APR 14 05:07:34 2016
Warning:aiowait timed out 1 times
Thu APR 14 05:07:34 2016
Warning:aiowait timed out 1 times
Thu APR 14 05:07:34 2016
Warning:aiowait timed out 1 times
Thu APR 14 05:07:34 2016
Warning:aiowait timed out 1 times
Thu APR 14 05:07:34 2016
Warning:aiowait timed out 1 times
Thu APR 14 05:07:35 2016
Warning:aiowait timed out 1 times
Thu APR 14 05:10:16 2016
Thread 1 cannot allocate new log, sequence 52199
is the Data warehouse system, the time is running batch process, I suspect is the Solaris asynchronous IO problem, is communicating with the manufacturer, there is no feedback.
--20160401
Changed the Disk_asynch_io, changed from true to False, no error, but the ETL is particularly slow, and changed back to true;
--20160414
Changed the db_writer_processes, changed from 20 to 28, observe the effect tonight;
This article from the "Iris" blog, reproduced please contact the author!
Solaris+oracle 11g warning:aiowait timed out 1 times