This post is about log writer (lgwr) IO.
It’s good to point out the environment on which I do my testing:
Linux X64 OL6u3, Oracle 184.108.40.206 (no BP), Clusterware 220.127.116.11, ASM, all database files in ASM.
In order to look at what the logwriter is doing, a 10046 trace of the lgwr at level 8 gives an overview.
A way of doing so is using oradebug. Be very careful about using oradebug on production environments, it can/may cause the instance to crash.
This is how I did it:
SYS@v11203 AS SYSDBA> oradebug setospid 2491
Oracle pid: 11, Unix process pid: 2491, image: firstname.lastname@example.org (LGWR)
SYS@v11203 AS SYSDBA> oradebug unlimit
SYS@v11203 AS SYSDBA> oradebug event 10046 trace name context forever, level 8
Of course 2491 is the Linux process id of the log writer, as is visible with “image”.