Re: DNS and SQL*Net Issue
Date: Tue, 26 Jan 2010 09:15:41 -0800 (PST)
From: Jared Still <jkstill_at_gmail.com>
If you haven't already, you may want to consider this doc: http://download.oracle.com/docs/cd/B28196_01/idmanage.1014/b15991/server.htm#i1053850
We found that while dynamic discovery worked well in the lab, when first tried in production it was very slow. This may lead to timeouts.
The problem was found to be that a nanosleep call from from 1-5 seconds was being inserted into every call. This is caused by Oracle receiving an error from DNS.
The cause of the error was that DNS was look for an LDAPS record in addition to the LDAP record. Create the LDAPS record fixed the problem.
Thanks for the information. What's curious is that the remote site is not using an LDAP server at all in there enclave. But reading the above link, it could be that the SRV record for the newly built server is not in the DNS. Perhaps this could be causing the extra delay? We're only listening on 1521 TCPS so we'd only ever see _ldaps._tcp._oid, right?
-- mohammed -- http://www.freelists.org/webpage/oracle-lReceived on Tue Jan 26 2010 - 11:15:41 CST