How To Track Dead Connection Detection(DCD) Mechanism Without Enabling Any Client/Server Network Tracing
Last updated on SEPTEMBER 04, 2017
Applies to:Oracle Net Services - Version 220.127.116.11 to 18.104.22.168 [Release 9.2 to 11.2]
Information in this document applies to any platform.
This may not be applicable to version 12. See the following document:
+ This requires truss/ strace / tusc or any system call trace tool & understanding on the system call functions.
+ The example here is taken from database server on solaris operation system for an dedicated server process
Abbreviation in this note are as follows,
DCD => Dead Connection Detection
DB => Database
PID => Process ID
The goal is check and confirm if DCD functionality or mechanism is
working as expected at the DB server side when you have enabled the
respective sqlnet.expire_time parameter.
That is to track if the timer is getting expired after specified interval and
DCD sending probe packets being written on to the tcp socket corresponding
to connected database server process for the respective client.
Especially, without enabling the client and server network traces or
in the case where the client has gone and session at server side is still present.
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