My Oracle Support Banner

OUD Error with Oracle Access Logger Enabled "Cannot decode the provided Execution Context control ..." when Using ECID Control "LDAP: error code 80" and "Invalid ECID" Accessing OUD via OVD Adapter or Other Integrated Applications (Doc ID 1485587.1)

Last updated on OCTOBER 23, 2023

Applies to:

Oracle Unified Directory - Version and later
Oracle Virtual Directory - Version to [Release 11g]
Information in this document applies to any platform.


Oracle Virtual Directory (OVD) 11g adapter and/or other applications integrated with Oracle Unified Directory (OUD) fail with error "Operations error - LDAP: error code 80" and "Invalid ECID" when Oracle Access Logger is enabled in OUD.

Application log error:

[2021-05-20T04:31:34.435+00:00] [<server>] [WARNING] [LIBOVD-40066] [oracle.ods.virtualization.engine.backend.jndi.OUDLdap] [ecid: <ecid>o,0:5:2:1:1:2:1:2:1:12:20:2:1:3:5:7:11:3:13:2:1:10:1:8:1:1:5:4:1:1:1:1:1:1:1:1] Remote Server Failure:<hostname>:<port>.[[javax.naming.NamingException: [LDAP: error code 80 - Worker Thread 13 encountered an uncaught exception while processing operation SearchOperation(connID=48193, opID=15, baseDN=<dn>, scope=sub, filter=(&(&(uid=*)

OUD 12c log error:

[25/May/2021:05:31:01 +0000] 6668 caught error thread={Worker Thread 3(229)} threadDetail={parentThread=main(1) isDaemon=false clientConnection=LDAP client connection from <ip>:<port> to <ip>:<port> operation=SearchOperation(connID=58970, opID=14986, baseDN=<dn>, scope=base, filter=(&(&(uid=*) } method={valueToControl(} caught={java.lang.IllegalArgumentException: Invalid ECID.uniqueId: 0:3:2:1:1:2:1:2:21:1:3:1:17:2:14:3:1:18:1:3:9:5:10:9:10:5:5:2:2:1:1:1:1:4:1:1:737}
Stack Trace:
 at oracle.core.ojdl.ECID.checkValid(
 at oracle.core.ojdl.ECID.parse(
 at org.opends.server.controls.ExecutionContextControl$Decoder.valueToControl(
 at org.opends.server.controls.ExecutionContextControl$Decoder.decode(
 at org.opends.server.controls.ExecutionContextControl$Decoder.decode(
 at org.opends.server.core.OperationWrapper.getControl(
 at org.opends.server.types.AbstractOperation.getRequestControl(
 at org.opends.server.loggers.OracleAccessLogPublisher.getOperationContext(
 at org.opends.server.loggers.OracleAccessLogPublisher.appendHeader(
 at org.opends.server.loggers.OracleAccessLogPublisher.logSearchRequest(
 at org.opends.server.loggers.AccessLogger.logSearchRequest(

Steps to reproduce the issue with OVD 11g integration:

1. Create a LDAP adapter for OUD in OVD.
2. Access the OUD data through OVD server using a ldapsearch command. 


ldapsearch -p <PORT> -D cn=orcladmin -w <PASSWORD> -s sub -b "ou=<OU>,dc=<COMPANY>,dc=com" "objectclass=*"

All entries are returned.
3. In OUD server, enable "Oracle Access Logger".
4. Repeat the ldapsearch command and it fails this time as follows:

ldapsearch -p <PORT> -D cn=orcladmin -w <PASSWORD> -s sub -b "ou=<OU>,dc=<COMPANY>,dc=com" "objectclass=*"
ldap_search: Operations error
ldap_search: additional info: LDAP Error 1 : [LDAP: error code 80 - Worker Thread 3 encountered an uncaught exception while processing operation
SearchOperation(connID=<CONN ID>, opID=2, baseDN=ou=<OU>,dc=<COMPANY>,dc=com, scope=wholeSubtree, filter=(objectclass=*)):  Invalid ECID:  <ECID> (]


Another Scenario without OVD integration:

OUD server or OUD Proxy server configured as per:    OUD - How to Configure and Use Execution Context ID (ECID) to Troubleshoot OUD Integration with Other Oracle Products (Doc ID 2197011.1)

Using command line ldap tools with ecid control (-J), for example:



Issue is reproduced when Oracle Access Logger is enabled in OUD.


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

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