Hi John,
I don't see "cn=MY_APP" in the connection string. Do you mean
"cn=OracleContext" after the first comma?
You seem to have two strings on one line separated by a space. Is it because
you have two LDAP servers ldap and ldapb load balanced? We used to use this
syntax but I remember the second part (after the space) also had to begin with
jdbc:oracle:thin:@, which you omitted. I'm not sure if that can be omitted.
(Ref: the example at the bottom of
http://docs.oracle.com/database/121/JJDBC/urls.htm)
Now we have a Cisco content switch in front of the two LDAP servers and our
syntax is shortened to one string, e.g.
db_url =
"jdbc:oracle:thin:@ldap://oidsvr.example.com:389/orcl,cn=OracleContext,dc=example,dc=com";;
where oidsvr.example.com is the switch. Using this switch not only simplifies
the syntax, but also makes it possible for some vendor software programs to use
Oracle LDAP for connect identifier resolution, because some of them don't
support the two string format.
Yong Huang
Get error [LDAP: error code 32 - No Such Object]; remaining name 'cn=MY_APP'...
when trying to connect with
jdbc:oracle:thin:@ldap://ldap.oracle.grp.net:389/MY_APP,cn=OracleContext,dc=oradb,dc=grp,dc=net
ldap://ldapb.oracle.grp.net:389/MY_APP,cn=OracleContext,dc=oradb,dc=grp,dc=net
It appears our code is parsing the string only up to the first comma, so it--
is truncating the connection string. Can another separator be used?
