Sql Execution Stuck on Wait Event "Disk File Operations I/O" after adding New DiskGroup
(Doc ID 2446479.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 and laterIBM AIX on POWER Systems (64-bit)
Symptoms
- ALL statement struck on wait event "Disk file operations I/O" with P1=2, P2=3117 and P3=1 on node 1 and all of application would be timeout.
- I/O subsystem performance is well within the recommended limits (i.e.) Average read (ms) But a few disk are bad performance.
- I/O subsystem performance is poor after restarting database and then application should be shutdown that system performance would be fine.
AWR report shows that Foreground Events are hugely waiting for "Disk file operations I/O"
Vmstat shows that CPU usage of sys is increasing from 43 to 54 CPU usage.
1. findings : CPU Usage (%) System Configuration: lcpu=144 mem=245760MB kthr memory page faults cpu System Configuration: lcpu=144 mem=245760MB kthr memory page faults cpu System Configuration: lcpu=144 mem=245760MB kthr memory page faults cpu 2. findings : Disk High Busy (%)
SnapTime Value DEVICE: hdisk10 3. findings : Disk High Service Time (mSec)
DEVICE: hdisk1377 DEVICE: hdisk796
Waiting for 'Disk file operations I/O' .. FileOperation=2 Top Event P1/P2/P3 Values Event % Event P1 Value, P2 Value, P3 Value % Activity Parameter 1 Parameter 2 Parameter 3
|
Changes
Add a New DiskGroup with incorrect RPM configurations.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |