Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MaxDB - Everything about MaxDB, formerly known as SAP DB
MySQL++ - Programming with the C++ API to MySQL
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
ODBC - ODBC with the MySQL Connector/ODBC driver
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
mysql openssl Question
mysql:it 's a db not a dbms how it 's possible?!
Does the binary log enabling affect the MySQL performances?
Strange behavior, Table Level Permission
FULLTEXT query format question
Preventing Duplicate Entries
Comparing and writing out BLOBS
Executing MySQL Commands From Within C Program
Can 't access mysql after kernel upgrade
Mysql 4 0 Oracle Stored Procedure Trigger Conversion
Downgrade Mysql from 4 to 3 23
MySQL Cluster Software
mysql test 4 1 fails with the gis test
ERROR 2002: Can 't connect to local MySQL server through socket
Getting Identity after INSERT
Update one field with more fields from another table
ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
mysql have same function mthod as Oracle decode()
 
myodbc connection problems

myodbc connection problems

2006-03-13       - By Mogens Lunde

 Back
Reply:     1     2  

I am using myodbc 3.51.12 where I observed a lot of #2013 errors "Cannot
connect to MySQL server". The main use is from MS-Access 2002 on my
Win-XP Pro SP-2 to access the MySQL databases residing on the webserver
at my webhost.

To remedy this problem I tried to add "set wait_timeout=999999" in
initial statement. This solved my connection problems, but gave a
problem as the web server administrator noticed a lot of pipes hanging
for several hours.

Then I tried to reduce this number to 200, and with this relatively low
value I were still able to use MS-Access. However, it seems as if the
old high wait_timeout value still remains, as the problem with hanging
pipes still exist.

If I remove the wait_timeout value entirely, I can only run 1-2 queries
- then I get these #2013 errors. When this happens I have to close down
MS-Access and restart. Then I have 1-2 "shots" again.

Therefore I would very much like to know how I can make sure that
1) My calls does not create load problems on the server
2) That I can use various queries without constantly getting #2013 errors.

Thank you

Mogens

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:    http://lists.mysql.com/myodbc?unsub=mysql@(protected)