OUD 11.1.2.3.1: Etime in Access Log is Rounded Up or Rounded Down (Doc ID 2079630.1)

Last updated on APRIL 03, 2023

Applies to:

Symptoms

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

Example#1:
When the elapsed time between REQ and RES is .007 (.300 - .293), the etime value is 0.

OUD Access Log (Oracle Access Logger)

Changes

The issue occurs after applying OUD Bundle Patch 11.1.2.3.1 (Patch 21370155).

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.