|
Windows 7 Pro, SQL Anywhere 10.0.0.2465 When I connect to a database on the machine in question using Sybase Central it connects in a couple of seconds or less, but when I do a test connection with the ODBC applet it takes more than two minutes to come back with a "connection successful" message. I'm having trouble with other software connecting also, but staying with the ODBC applet keeps things simple and I think that solving the problem with the applet will solve my other problems, Brian Scanlon Spectra Data Systems |
|
Could setting the host for the machine the server is running on possibly help out? We've ran into issues before when the application has to search for the database server. However, when we set the host it's almost instantanious. HTH. Jeff Gibson The server is running on the same machine.
(28 Nov '11, 19:21)
Brian S
Replies hidden
1
Do you use a shared Memory Connection or TCP/IP ? In case of TCP you can try to add dobroad=none as Parameter.
(29 Nov '11, 07:30)
Thomas Dueme...
|
What are your connection parameters when using ODBC?
I suggest you add LOGFILE=<file> to both connection strings. For example LOGFILE=c:cli.out. Then try a connection both from Sybase Central and from ODBC. After that the file (say cli.out) will show the connection string actually used to connect (after combining the connection string, DSN and SQLCONNECT environment variable), and it will show the steps being taken to connect.
Hopefully you will see the difference after comparing the two connections. If not, post the logfile, as well as the server command line. It would be helpful if you post the host and IP address of both the client machine and the server machine. Given that information we should be able to help.
FYI, 10.0.0 is nearing the end of its engineering support (I believe it ends at the end of 2011, but I'm not positive), and you have a very old build as 10.0.1 still has limited support, but 10.0.0 has not been supported for several years. That said, if you aren't actually having a problem, you don't need to upgrade to the current 10.0.1 build.
Ok, have more clues as to shat is going on. It look like the problem is that the shared memory connection is failing. If I remove the SharedMemory from the links everything is fine. I have used this on many other machines and never had this problem. (yes the server and the client are on the same machine)
Tue Nov 29 2011 09:06:50 09:06:50 Attempting to connect using: UID=dba;PWD=**;ENG=Gate;CON=SQL_DBC_ee2ec48;ASTOP=YES;INT=NO;LTO=600;LOG=c:tempodbclog.txt;LINKS='tcpip{host=DEV1003},SharedMemory';COMP=NO 09:06:50 Attempting to connect to a running server... 09:06:50 Trying to start SharedMemory link ...
09:06:50 SharedMemory link started successfully
09:06:50 Attempting SharedMemory connection (no sasrv.ini cached address)
09:08:52 Failed to connect over SharedMemory
09:08:52 Removing failed address from sasrv.ini cache
So your server doesn't support a shared memory link? Is there any reason it doesn't?
Do your client and the database server run in different sessions? - IIRC, newer Windows Server versions (including Win7) may not support ShMem between services and clients in different sessions. Cf. this FAQ...
The server claimed the the SharedMemory link was started sucessfully.
When your application and Sybase Central are connected, what does sa_conn_info() reveal? Are both connections via TCP/IP?
Besides, you may also try to use the server's network connections with dbsrv10 -z -o MyLog.Txt