How to Match Oracle Net Client and Server Trace Files
Last updated on JUNE 12, 2017
Applies to:Oracle Net Services - Version 184.108.40.206 to 220.127.116.11.0 [Release 9.2 to 12.2]
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms