OUD 12c Client Connection Details (conn_details / log-connection-details) Lines are Duplicated in the Admin Log
(Doc ID 2975823.1)
Last updated on SEPTEMBER 27, 2023
Applies to:Oracle Unified Directory - Version 22.214.171.124.230406 and later
Information in this document applies to any platform.
Oracle Unified Directory (OUD) 12c client connection details (conn_details) lines are duplicated in the admin file based logger.
Configured connection details as per the following documentation:
Oracle® Fusion Middleware Administering Oracle Unified Directory 12c (126.96.36.199.0)
Chapter 35 Monitoring Oracle Unified Directory
Section 188.8.131.52.6 Logging Additional Connection Details
OUD 12c - Log Publisher Property "log-connection-details" Stops Working after Restart (Doc ID 2892360.1)
OUD12c - The Hostname of the Backend Server is Incorrectly Identified by the "s_conn" Value in the File Access Logger when the "log-connection-details" is Enabled in OUD Proxy (Doc ID 2893637.1)
When connection detail logging is enabled for access and admin loggers, the CONN_DETAILS line is duplicated in the admin log for some client connections.
For example, in admin log:
When admin connection details is set to false, the server does not experience the duplication. Setting admin connection details to true results in the duplication.
The the issue can go both ways. It may take one hour of admin and access logs to then find that every CONN_DETAIL entry occurs in both logs, regardless of whether the connection was made to a client or admin port. The order might be different when more than one connection happens during the same second.
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