ODSM to OVD 11g Data Browser Hangs with Error OVD-60182 "Provided Value Cannot Be Parsed As A Valid Distinguished Name" in the Log OR ldapbind Fails
(Doc ID 1285404.1)
Last updated on AUGUST 30, 2023
Applies to:
Oracle Virtual Directory - Version 11.1.1.1.0 to 11.1.1.3.0 [Release 11g]Information in this document applies to any platform.
Symptoms
Symptom 1:
- OVD 11.1.1.2
- LDAP Adapter created for ODSEE
- Accessing the data via client view from ODSM hangs
- Log shows the following error:
[2010-12-29T10:18:41.506-05:00] [octetstring] [ERROR] [OVD-60182] [com.octetstring.vde.MessageHandler] [tid: <TID>] [ecid: <ECID>] [arg: java.lang.IllegalArgumentException:
com.octetstring.vde.util.InvalidDNException: Provided value cannot be parsed as a valid distinguished name.] Exception:
java.lang.IllegalArgumentException:
com.octetstring.vde.util.InvalidDNException: Provided value cannot be parsed as a valid distinguished name..[[
java.lang.IllegalArgumentException:
com.octetstring.vde.util.InvalidDNException: Provided value cannot be parsed as a valid distinguished name.
com.octetstring.vde.util.InvalidDNException: Provided value cannot be parsed as a valid distinguished name.] Exception:
java.lang.IllegalArgumentException:
com.octetstring.vde.util.InvalidDNException: Provided value cannot be parsed as a valid distinguished name..[[
java.lang.IllegalArgumentException:
com.octetstring.vde.util.InvalidDNException: Provided value cannot be parsed as a valid distinguished name.
OR
Symptom 2:
Sometimes LDAP BIND fails with error 49 in access.log:
[2019-05-16T14:10:47.560+02:00] [octetstring] [NOTIFICATION] [OVD-20038] [com.octetstring.accesslog] [tid: <TID>] [ecid:<ECID> conn=53 364 op=229 BIND dn=uid=XXXXXX,ou=xxx,o=xxxx method=0 version=3
[2019-05-16T14:10:49.501+02:00] [octetstring] [NOTIFICATION] [OVD-20039] [com.octetstring.accesslog] [tid: <TID>] [ecid: <ECID> conn=53 364 op=229 RESULT err=49 tag=0 nentries=0 etime={3}
[2019-05-16T14:10:49.501+02:00] [octetstring] [NOTIFICATION] [OVD-20039] [com.octetstring.accesslog] [tid: <TID>] [ecid: <ECID> conn=53 364 op=229 RESULT err=49 tag=0 nentries=0 etime={3}
However in diagnostic.log file, for the same ecid, following error appears :
[2019-05-16T14:10:49.484+02:00] [octetstring] [ERROR] [OVD-60060] [com.octetstring.vde.operation.BindOperation] [tid: <TID>] [ecid: <ECID> An error occurred.[[
com.octetstring.vde.util.InvalidDNException: Provided value cannot be parsed as a valid distinguished name.
at com.octetstring.vde.syntax.DistinguishedName.decode(DistinguishedName.java:475)
at com.octetstring.vde.syntax.DistinguishedName.(DistinguishedName.java:121)
at com.octetstring.vde.syntax.DistinguishedName.toDNSyntax(DistinguishedName.java:431)
at com.octetstring.vde.chain.plugins.upnbind.UPNBindPlugin.bind(UPNBindPlugin.java:137)
at com.octetstring.vde.chain.Chain.nextBind(Chain.java:233)
at com.octetstring.vde.chain.plugins.performance.MonitorPerformance.bind(MonitorPerformance.java:333)
...
at com.octetstring.vde.operation.BindOperation.run(BindOperation.java:252)
at com.octetstring.vde.operation.AbstractOperation.perform(AbstractOperation.java:122)
at com.octetstring.vde.MessageHandler.doBind(MessageHandler.java:354)
at com.octetstring.vde.MessageHandler.answerRequest(MessageHandler.java:194)
at com.octetstring.vde.OperationHandler.run(OperationHandler.java:119)
Caused by: javax.naming.InvalidNameException: Invalid name: XXXXXX
at javax.naming.ldap.Rfc2253Parser.doParse(Rfc2253Parser.java:111)
...
com.octetstring.vde.util.InvalidDNException: Provided value cannot be parsed as a valid distinguished name.
at com.octetstring.vde.syntax.DistinguishedName.decode(DistinguishedName.java:475)
at com.octetstring.vde.syntax.DistinguishedName.(DistinguishedName.java:121)
at com.octetstring.vde.syntax.DistinguishedName.toDNSyntax(DistinguishedName.java:431)
at com.octetstring.vde.chain.plugins.upnbind.UPNBindPlugin.bind(UPNBindPlugin.java:137)
at com.octetstring.vde.chain.Chain.nextBind(Chain.java:233)
at com.octetstring.vde.chain.plugins.performance.MonitorPerformance.bind(MonitorPerformance.java:333)
...
at com.octetstring.vde.operation.BindOperation.run(BindOperation.java:252)
at com.octetstring.vde.operation.AbstractOperation.perform(AbstractOperation.java:122)
at com.octetstring.vde.MessageHandler.doBind(MessageHandler.java:354)
at com.octetstring.vde.MessageHandler.answerRequest(MessageHandler.java:194)
at com.octetstring.vde.OperationHandler.run(OperationHandler.java:119)
Caused by: javax.naming.InvalidNameException: Invalid name: XXXXXX
at javax.naming.ldap.Rfc2253Parser.doParse(Rfc2253Parser.java:111)
...
Changes
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 |