sqysl你好,谢谢回复。我做了一个诊断,其中的一部分,感觉问题稍微还是在写上呢?
APPROACH: What is LGWR doing when 'log file sync' waits
are happening? LMS info may be relevent for broadcast
on commit and LNS data may be relevant for dataguard.
If more details are needed see the ASH DETAILS FOR WORST
MINUTES section at the bottom of the report.
MINUTE INST PROGRAM EVENT TOTAL_WAIT_TIME WAITS AVG_TIME_WAITED
------------ ---- ---------------------------------------- ------------------------------ ----------------- ---------- -----------------
5月 16_1523 1 JDBC Thin Client log file sync 2083.778 34 61.288
5月 16_1523 1 oracle@rac1 (LGWR) log file parallel write 443.098 22 20.141
5月 16_1523 1 oracle@rac1 (LGWR) .000 18 .000
5月 16_1523 1 oracle@rac1 (LMS0) gcs log flush sync 10.370 4 2.593
5月 16_1523 1 oracle@rac1 (LMS0) .000 10 .000
5月 16_1523 1 oracle@rac1 (LMS1) gcs log flush sync 1.471 2 .736
5月 16_1523 1 oracle@rac1 (LMS1) .000 15 .000
5月 16_1523 1 oracle@rac1 (LMS2) gcs log flush sync 6.128 6 1.021
5月 16_1523 1 oracle@rac1 (LMS2) .000 1 .000
5月 16_1523 1 oracle@rac1 (LMS3) gcs log flush sync 4.994 4 1.249
5月 16_1523 1 oracle@rac1 (LMS3) .000 3 .000
5月 16_1523 1 oracle@rac1 (LMS4) gcs log flush sync 15.870 4 3.968
5月 16_1523 1 oracle@rac1 (LMS4) .000 4 .000
5月 16_1523 1 oracle@rac1 (LMS5) gcs log flush sync 9.488 6 1.581
5月 16_1523 1 oracle@rac1 (LMS5) .000 9 .000
5月 16_1523 1 oracle@rac1 (LMS6) gcs log flush sync 5.384 6 .897
5月 16_1523 1 oracle@rac1 (LMS6) .000 9 .000
5月 16_1523 2 JDBC Thin Client log file sync 86.303 10 8.630
5月 16_1523 2 oracle@rac2 (LGWR) log file parallel write 36.724 4 9.181
5月 16_1523 2 oracle@rac2 (LGWR) control file sequential read .390 1 .390
5月 16_1523 2 oracle@rac2 (LGWR) .000 4 .000
5月 16_1523 2 oracle@rac2 (LMS0) .000 5 .000
5月 16_1523 2 oracle@rac2 (LMS1) .000 6 .000
5月 16_1523 2 oracle@rac2 (LMS2) .000 6 .000
5月 16_1523 2 oracle@rac2 (LMS3) .000 3 .000
5月 16_1523 2 oracle@rac2 (LMS4) .000 3 .000
5月 16_1523 2 oracle@rac2 (LMS5) .000 3 .000
5月 16_1523 2 oracle@rac2 (LMS6) .000 6 .000