One of our users is running a query against our linux database server running Percona-Server-server-56-5.6.51-rel91.0.1.el7.x86_64. They receive:
DatabaseError: (mysql.connector.errors.DatabaseError) 1205 (HY000): Lock wait timeout exceeded; try restarting transaction…
On the server, we are getting the error:
2022-02-03 07:41:38 16489 [ERROR] /usr/sbin/mysqld: Can’t find file: ‘200_Character_SELECT_call’ (errno: 36 - File name too long)
200_Character_SELECT_call is the obfuscated version of an actual DB/Select@ call
I googled and found very little info. Is this an OS limitation we can fix, or would we need to upgrade Percona?
Hi @miles.lott , thanks for posting to the Percona forums!
You’re right, Percona Server 5.6 reached EOL February 2021 so it is now a year out of support (unless you have a commercial relationship with Percona - if that’s the case, DM me and I’ll escalate you to the Support team). So you should upgrade to 5.7 and we would be happy to help you troubleshoot your query.
In terms of your error on 5.6 , I would be surprised if there is a limit at 200 characters - i have had customers share queries that span 20k characters or more. If you can share the table schema and the full query we can see if we can reproduce on 5.7 and let you know if this is an ongoing issue or not.
I think the 200 character limit is only due to a limit of what is shown in the error. They managed to fix this by setting chunk size on the client. Main issue is that their dataset has grown to the point where they are manipulating a lot more with multiple likes and what not Thanks for your concern. I believe we do have a support contract, or did, and plan to migrate to 5.7 as soon as is feasible.
Glad you found a workaround. Thanks again for posting to the forums so that others will find your solution!