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 11.1.1.5.0 and laterOracle Virtual Directory - Version 11.1.1.1.0 to 11.1.1.9.0 [Release 11g]
Information in this document applies to any platform.
Symptoms
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:
OUD 12c log error:
Stack Trace:
at oracle.core.ojdl.ECID.checkValid(ECID.java:146)
at oracle.core.ojdl.ECID.parse(ECID.java:127)
at org.opends.server.controls.ExecutionContextControl$Decoder.valueToControl(ExecutionContextControl.java:125)
at org.opends.server.controls.ExecutionContextControl$Decoder.decode(ExecutionContextControl.java:78)
at org.opends.server.controls.ExecutionContextControl$Decoder.decode(ExecutionContextControl.java:61)
at org.opends.server.core.OperationWrapper.getControl(OperationWrapper.java:852)
at org.opends.server.types.AbstractOperation.getRequestControl(AbstractOperation.java:515)
at org.opends.server.loggers.OracleAccessLogPublisher.getOperationContext(OracleAccessLogPublisher.java:1867)
at org.opends.server.loggers.OracleAccessLogPublisher.appendHeader(OracleAccessLogPublisher.java:1755)
at org.opends.server.loggers.OracleAccessLogPublisher.logSearchRequest(OracleAccessLogPublisher.java:1539)
at org.opends.server.loggers.AccessLogger.logSearchRequest(AccessLogger.java:1138)
at org.opends.server.core.SearchOperationBasis.run(SearchOperationBasis.java:1494)
at org.opends.server.extensions.TraditionalWorkerThread.run(TraditionalWorkerThread.java:166)
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.
Example:
All entries are returned.
3. In OUD server, enable "Oracle Access Logger".
4. Repeat the ldapsearch command and it fails this time as follows:
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> (ECID.java:115 ExecutionContextControl.java:127 ExecutionContextControl.java:72 ExecutionContextControl.java:57 AbstractOperation.java:406 OracleAccessLogPublisher.java:1664 OracleAccessLogPublisher.java:1455 AccessLogger.java:1061 SearchOperationBasis.java:1316 TraditionalWorkerThread.java:166)]
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:
Changes
Issue is reproduced when Oracle Access Logger is enabled in OUD.
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |