--- On Wed, 5/5/10, Jared Still <jkstill@xxxxxxxxx> wrote: On Wed, May 5, 2010 at 9:16 AM, Yong Huang <yong321@xxxxxxxxx> wrote: I tried to reproduce this but can't. My test with 10.2.0.1 Oracle on Windows XP shows that the name (connection string) is still instantly resolved and tnsping returns OK if the first OID server is unreachable (can ping, but OID port is closed because there's no OID software installed) or if its name can't be resolved by DNS. I also tried this with 11gR2 and 10.2.0.4 Oracle on 64-bit Linux. I've reproduced this from windows and linux clients and OID servers on linux. The ldap.ora was identical to yours other than the server names. Shutting down OID on server1 caused a lengthy timeout until server2 was used to resolve the name. When you tested was the physical server available or unavailable? Jared, I tested two cases: (1) server1 is a hostname pingable but has no OID software installed on it (and ports 389 and 636 are not open), and (2) server1 is a hostname that cannot be resolved by either hosts file or DNS. If by "physical server", you mean the DB server the connection string points to, then it's always up and running. There's only one case I can reproduce hung access to OID (and tnsping hangs exactly 2 minutes on both Windows and Linux): server1 is a pingable host and the ports in ldap.ora are open, but they're not OID's ports. For example: DIRECTORY_SERVERS= (server1:22:22,server2:389:636) where server1 is a Linux box accessible through ssh and server2 has OID running on it. I don't know why I can't reproduce your and Chris's scenario. Our OID server uses 10gR1 Oracle database and runs on Windows. Yong Huang