Sorry for the horrible latency! We've had a problem with our notification gizmo on this forum and didn't realize it.
Your second mrskew command doesn't show any information about sqlid because your command line didn't ask for it; that is, you didn't refer to $sqlid in the --group expression.
The third one is giving you the best it can. The only read calls in the trace file for which $p3==1 were associated with cursor id #0, which is never associated with a specific SQL statement. Cursor #0 is generally how Oracle maps implicit COMMIT workload and LOB processing. When there is no sqlid for a given call, mrskew tries to be as helpful as it can by giving you the cursor id.
Hope this helps,
The administrator has disabled public write access.