OUD 220.127.116.11.1: Etime in Access Log is Rounded Up or Rounded Down
(Doc ID 2079630.1)
Last updated on DECEMBER 27, 2021
Applies to:Oracle Unified Directory - Version 18.104.22.168.1 and later
Information in this document applies to any platform.
The "etime" in Oracle Unified Directory Access Log is not recorded correctly.
If the actual elapsed time is a short time, the etime value is rounded up or rounded down.
If the actual elapsed time is under some dozens of milliseconds, the etime value is rounded down to 0.
If the actual elapsed time is over some dozens of milliseconds, the etime value is rounded up to 200.
If the actual elapsed time is a long time, the etime value is the same as it.
The issue is independent of the types of LDAP requests. The issue occurs with the following LDAP requests;
BIND, SEARCH, ADD, MODIFY, DELETE, COMPARE
When the elapsed time between REQ and RES is .007 (.300 - .293), the etime value is 0.
OUD Access Log (Oracle Access Logger)
The issue occurs after applying OUD Bundle Patch 22.214.171.124.1 (Patch 21370155).
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