In my previous post Are you fishing or catching? – Server-side SQL*Net tracing for specific clients I said SQL*Net tracing is all or nothing as sqlnet.ora entries apply to all server processes. I since learned that there is a “oradebug” command to enable SQL*Net tracing for individual server processes:

oradebug setospid <OSPID>
oradebug dump sqlnet_server_trace <LEVEL>

Available levels are the same as for TRACE_LEVEL_SERVER in sqlnet.ora (0,4,10,16).

This is a nice little addition to my toolset. The only drawback is that you cannot trace initial connection hand-shakes (e.g. SSL troubleshooting) as you have to attach to a existing process.