Oracle Database / Sessions, Locks & Transactions
Map an Oracle session to its server process
Host CPU or a trace file may name a process rather than a database session. Join the session and process views before escalating.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
SELECT s.sid, s.serial#, s.username, p.spid, p.tracefile FROM v$session s JOIN v$process p ON s.paddr = p.addr WHERE s.type = 'USER';Read the result
SPID identifies the server process in this instance. Shared-server, threaded and pooled configurations need additional interpretation rather than a one-session-one-process assumption.
Resolve and verify
Match the OS sample time and process to SQL, waits and the relevant trace. Use instance-aware joins when performing the same investigation across RAC.
Operational precautions
Do not send operating-system kill signals to an Oracle process as a routine diagnostic action.