as you asked for tracing, a "normal" 10046 trace can be enabled for
You will not get SQL statements, but normal trace information regarding
The event log file parallel write is somehow tricky. Frits wrote a nice blog
It's important to understand that it represents multiple IOs (that's the
"EMC and sysadmins have confirmed there are no disk errors and from theirstandpoint the disks are waiting on Oracle."
Folks, I've got a bit of a mystery with a particular db where we're
getting a periodic 25-30 pause between user sessions and LGWR processes and
can't clearly identify what's the cause.
- The database is 184.108.40.206, RHEL 7.5, running ASM on EMC.
- Sometimes once a day, sometimes more (never more than 5) times a day
we see user processes start waiting on "log file sync". LGWR is waiting on
"log file parallel write".
- At the same time one of the emcpower* devices shows 100% busy and
service time 200+ (from iostat via osw). mpstat shows 1 CPU at 100% on
iowait. It's not always the same disk (emcpowere1, a1, h1, …), not always
the same CPU. EMC and sysadmins have confirmed there are no disk errors
and from their standpoint the disks are waiting on Oracle.
- During this time LGWR stats in ASH are all 0 - TIME_WAITED, DELTA*
columns. Only after the problem goes away (about 25 secs) these columns
are populated again, obviously the DELTA* columns 1 row later. LGWR's
session state is WAITING so I assume the column value observations are due
to LGWR waiting, as it won't write stats until it can do something.
I am stuck trying to find out, really prove who is the culprit or what
exactly the wait is on. Is LGWR waiting on user sessions and user sessions
are waiting on LGWR and all that causes the disk to be 100%? Can I enable
some sort of tracing on LGWR and would that point to exactly what he's
waiting on to prove where the problem is?