I just executed a perl file with a mysql instruction at the begining of it. This mysql instruction is very simple and should not last more than a few seconds. However, it stays in either "locked", "system lock" or "reopen tables" status, and it does not continue, even when there is no other process running. This happens to me sometimes (not all the time) when I execute some perl files with mysql querys, from the ssh interface. Is there a way to avoid that? Is it a bug from mysql or I'm doing something wrong? Is it a problem of the server? (it's by the way a very good dedicated server and I'm paying a lot of money for it). Is there a way to avoid this problem from happening again?? Thanks a lot in advance!!!
2006-10-05 21:38:23 · 1 answers · asked by Anonymous 1 in Computers & Internet ➔ Programming & Design
Hello, Try contacting your ISP, it seems like they are setting LOCK TABLES restrictions on your account. It assumes your server has many users and performing a deadlock.
Take a look at this link to see the exact scenario:
http://www.xaprb.com/blog/2006/07/31/how-to-analyze-innodb-mysql-locks/
Good Luck
2006-10-06 04:57:14 · answer #1 · answered by ? 6 · 0⤊ 0⤋