Re: More info about 40001 SQL_NO_CACHE
The only time I ever saw a message just hang out in the processlist like that is when I ran a mysqldump and piped it directly to mysql to load data directly from one MySQL server to another. While doing this, the target MySQL system ran out of room on the mounted drive where the datadir was pointing. So the message you seeing I also saw from the source machine. MySQL is a little polite in this matter. I just pauses and waits until there is more room on the available target's datadir to continue send more data to the target. From what you described, you problem sounds very simple yet complicated. Try to find out what software issued that SQL statement and its intended target. - Original Message - From: Connie A. Logg [EMAIL PROTECTED] To: mysql@lists.mysql.com Sent: Wednesday, November 15, 2006 11:18:31 PM GMT-0500 US/Eastern Subject: More info about 40001 SQL_NO_CACHE This showed up in 'show processlist' and it had had an active time of about 4 days. Numerous other inquiries were hung behind it, although the other inquiries completed eventually...but they were so slow as to backup the data base entry code and extraditions for the analysis by several hours. Can someone please enlightn me on this problem? Like I mentioned, the web search entries indicated that this hanging was a mysql problem. I have upgraded to 5.0.27. But I will not know until tomorrow if the mysqldump that I do tonight works. -Original Message- From: Logg, Connie A. [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 15, 2006 11:41 AM To: mysql@lists.mysql.com Subject: SELECT /*!40001 SQL_NO_CACHE */ * FROM `ROUTEDATA` message I am running mysql version 5.0.24 and am seeing this error when running mysqldump. From what I can find on the web, this message is generated by an error in the mysql code. Please correct me if I am wrong. Is this fixed in mysql 5.0.27 ? Thanks, Connie Logg, Network Analyst Stanford Linear Accelerator Center ph: 650-926-2879 Happiness is found along the way, not at the end of the road, and 'IF' is the middle word in life. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: More info about 40001 SQL_NO_CACHE
Thank you...All I was doing was a musqldump of the tables in my data base to files, one file for each table. Yesterday I upgraded to mysql 5.0.27, so I will watch it for a while. It just started happening last Saturday night, and I had been running the system for a few months. Thanks for you response. Connie Logg, Network Analyst Stanford Linear Accelerator Center ph: 650-926-2879 Happiness is found along the way, not at the end of the road, and 'IF' is the middle word in life. From: Howard Hart [mailto:[EMAIL PROTECTED] Sent: Thursday, November 16, 2006 8:41 AM To: Logg, Connie A. Subject: RE: More info about 40001 SQL_NO_CACHE Looks like this may have been fixed in 5.0.25 or above, so if it's the same bug, you're good to go. http://bugs.mysql.com/bug.php?id=21288 Howard -Original Message- From: Logg, Connie A. [mailto:[EMAIL PROTECTED] Sent: Wed 11/15/2006 8:18 PM To: mysql@lists.mysql.com Subject: More info about 40001 SQL_NO_CACHE This showed up in 'show processlist' and it had had an active time of about 4 days. Numerous other inquiries were hung behind it, although the other inquiries completed eventually...but they were so slow as to backup the data base entry code and extraditions for the analysis by several hours. Can someone please enlightn me on this problem? Like I mentioned, the web search entries indicated that this hanging was a mysql problem. I have upgraded to 5.0.27. But I will not know until tomorrow if the mysqldump that I do tonight works. -Original Message- From: Logg, Connie A. [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 15, 2006 11:41 AM To: mysql@lists.mysql.com Subject: SELECT /*!40001 SQL_NO_CACHE */ * FROM `ROUTEDATA` message I am running mysql version 5.0.24 and am seeing this error when running mysqldump. From what I can find on the web, this message is generated by an error in the mysql code. Please correct me if I am wrong. Is this fixed in mysql 5.0.27 ? Thanks, Connie Logg, Network Analyst Stanford Linear Accelerator Center ph: 650-926-2879 Happiness is found along the way, not at the end of the road, and 'IF' is the middle word in life. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
