How to Match Oracle Net Client and Server Trace Files
(Doc ID 374116.1)
Last updated on MARCH 29, 2019
Applies to:Oracle Net Services - Version 22.214.171.124 to 126.96.36.199.0 [Release 9.2 to 12.2]
Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 12.1]
Information in this document applies to any platform.
Note that this document was created with non ADR or legacy style Oracle Net tracing in mind. In other words, the SQLNET.ORA file trace parameters would include: DIAG_ADR_ENABLED=off
Describes how to match Oracle Net client and server trace files that are collected simultaneously or that are 'matching'.
Using the characters in the AUTH_SESSKEY packet to determine which client trace matches a particular server trace or vice versa.
An alternate method of matching client to server traces is to use the unique Connection ID that's posted to each file at connect time.
See below for a detailed description.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document