DCD Does Not Work Due To Issue On Firewall In Some Environments
(Doc ID 2877995.1)
Last updated on JANUARY 22, 2025
Applies to:
Oracle Database Cloud Exadata Service - Version N/A and laterOracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Gen 2 Exadata Cloud at Customer - Version N/A and later
Oracle Database - Enterprise Edition - Version 19.24.0.0.0 and later
Information in this document applies to any platform.
Symptoms
DCD(Dead Connection Detection) does not work and server processes count reduces after some time from 720 to 389 seen in ps data of OSWatcher.
Such server processes are identified by '(LOCAL=NO)'.
According to design, DCD packet should be regularly sent to client process in the interval of sqlnet.expire_time,
and gets acknoledgement from client:
Example:
Cause
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
Symptoms |
Cause |
Solution |
References |