Execution context ID (ECID) is a unique identifier to correlate events or requests associated with the same transation across several components.
The ECID value for a particular request is generated at the first layer and is passed down to the subsequent layers. The ECID value is logged (and auditable) in each product involved in the transaction. ECID allows an administrator to track the end-to-end flow of a particular request across the product stack.
ECID are supported by OUD and can be used to track LDAP requests from the client down to the ultimate LDAP server processing the request (inclusing LDAP access layer/proxy if any).
When performing a LDAP operation, a client can pass a ECID using the LDAP control extension 2.16.840.1.113822.214.171.124 . This ECID is logged by OUD. The OUD server generates a ECID in case none is present in the incoming request.
ECID are logged in the “Oracle Access Logger”. By default, this logger is disabled. To enable it, run the command below:
dsconfig set-log-publisher-prop \
–publisher-name Oracle\ Access\ Logger \
–port <admin port>\
–bindDN cn=Directory\ Manager \
–bindPassword ****** \
Here is a sniplet of the Oracle access log:
[2012-08-16T16:10:26.770+02:00] [OUD] [TRACE] [OUD-24641559] [PROTOCOL] [host: prehnite] [nwaddr: 10.166.70.62] [tid: 25] [userId: sduloutr] [ecid: 10.166.70.62:37126:1345126226770:39,0] [category: REQ] [conn: -1] [op: 80] [msgID: 81] [dn: o=example] [type: synchronization] MODIFY
The administrator can then search the logs using a particular ECID value. Audit logs can be queried for a given ECID through Oracle BI Publisher’s audit reports. For example, if you send an LDAP request to Oracle Virtual Directory front-ending Oracle Unified Directory, an ECID associated with the LDAP request is present in the OVD diagnostic logs and audit logs; similarly, when the query reaches OUD, OUD includes the same ECID in its diagnostic logs and audit reports.