HansF schreef:
> Ran into this today ... (default App Sserver 10.1.2.0.2 install on
> Win2003)
>
> I configured the sqlnet.ora to look at LDAP first, then tnsnames, onames
> and host. Then I set up the ldap.ora in the ORACLE_HOME/network/admin to
> use a custom port (not the default 389)
>
> It didn't find the LDAP entry, although the entry was clearly uses from
> another machine.
>
> Searching, I found ORACLE_HOME/ldap/admin/ldap.ora with default port 389
> settings. Changed that port and all works as expected.
>
> Turns out this is documented. In the database Networking Reference manual
> http://download-west.oracle.com/docs/cd/B19306_01/network.102/b14213/ldap.htm#sthref969
> Of course, the tool used by the app server OUI is well documented ...
>
>
> Question:
>
> Has anyone run into an issue using one centralized OiD for TNS resolution,
> and a completely separate OiD for SSO? Any impact or concern?
>
>
Fail to see when ONAMES comes in - that was phased
out when 8 or 8i was phased out. Doesn't harm, tho,
but I'd rather have LDAP, TNSNAMES, EZNAME - in that
sequence for your case.
About your question: have not used your scenario, but
would not be surprised to find a product, or
installation, or combination, that does
not support this scenario of two LDAP servers.
I'd stick to one - if load is a problem, balance. But
somehow I doubt that load is the issue at hand here...
--
Regards,
Frank van Bortel
Top-posting is one way to shut me up...
Received on Sat Feb 17 2007 - 07:14:53 CST
