on 11-07-2007 11:19 PM
Set up a test database using 7.6.3.7 Windows x64 for a possible move to MaxDB on Server 2003 EE using 4 dual-core Opteron processors & 32 GB memory. Data storage will be to a 4GB fiber channel SAN initial data area approx 250GB.
Establishing database connections via ODBC or ADO.NET (I've tried both) is taking around 5-10 seconds for each connection and all database transactional traffic seems to be suspended while waiting for new database connections to be established.
We currently have a similar DB (7.6.0.12 with similar DB parameters) running on the Solaris platform (with a similar 2GB FC SAN) and experience no delay in establishing DB connections (sub second connection times are normal).
Any ideas on what may be causing the slow connections under Server 2003 EE x64?
Interestingly this was not related to the server DNS, but the client DNS. After doing a port capture of a connecting client, I could see where the client (ODBC) was requesting to resolve the host name for the IP. Since the server resides in a secure VLAN, I was able to solve by updating the client hosts file.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can the connecting client names be resolved by the server? I mean, is DNS for the server properly configured?
On each connection attempt the x_server tries to resolve the client name, what you may see is the DNS request timing out.
--
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.