Last updated on NOVEMBER 29, 2015
Applies to:Oracle Unified Directory - Version 126.96.36.199.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 short time, the etime value is rounded up or rounded down.
If the actual elapsed time is under some dozens millisecond, the etime value is rounded down to 0.
If the actual elapsed time is over some dozens millisecond, the etime value is rounded up to 200.
If the actual elapsed time is long time, the etime value is the same as it.
The issue is independent of 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 valus is 0.
OUD Access Log (Oracle Access Logger)
The issue occurs after applying OUD Bundle Patch 188.8.131.52.1 (Patch 21370155).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms