In this article, you will find a list of the most popular MySQL/MariaDB Error Codes and how to fix them.
If you don’t have full access to your server, please get in touch with your hosting provider and ask if they can increase or remove these limits.
Contents
MAX_CONNECTIONS_PER_HOUR
This error code refers to the maximum connections established to a MySQL server within an hour. If the limit is exceeded, the server will start rejecting connection requests and return an error message with the code “1040 – Too many connections.” This error can occur when the server is under heavy load, or when there are too many concurrent connection attempts from the same user.
To resolve this error, you can try increasing the value of the MAX_CONNECTIONS_PER_HOUR system variable, which sets the maximum number of connections allowed per hour. Alternatively, you can optimize your application to reduce the number of unnecessary connections and ensure that idle connections are closed properly.
MAX_USER_CONNECTIONS
This error code refers to the maximum number of connections a single user can establish to a MySQL server simultaneously. If the limit is exceeded, the server will return an error message with the code “1226 – User ‘username’ has exceeded the ‘max_user_connections’ resource.” This error can occur when a user’s application makes too many connections to the server or when multiple applications use the same user account.
To resolve this error, you can try increasing the value of the MAX_USER_CONNECTIONS system variable, which sets the maximum number of connections allowed per user. Alternatively, you can review your application’s connection usage and optimize it to reduce needed connections.
MAX_QUERIES_PER_HOUR
This error code refers to the maximum number of database queries executed on a MySQL server within an hour. If the limit is exceeded, the server will return an error message with the code “1226 – User ‘username’ has exceeded the ‘max_queries_per_hour’ resource.” This error can occur when an application makes too many queries to the server or when multiple applications use the same user account.
To resolve this error, you can try increasing the value of the MAX_QUERIES_PER_HOUR system variable, which sets the maximum number of queries allowed per user per hour. Alternatively, you can optimize your application to reduce the number of unnecessary queries and ensure that queries are properly optimized.
MAX_UPDATES_PER_HOUR
This error code refers to the maximum number of database updates that can be made on a MySQL server within an hour. If the limit is exceeded, the server will return an error message with the code “1226 – User ‘username’ has exceeded the ‘max_updates_per_hour’ resource.” This error can occur when an application makes too many updates to the server or when multiple applications use the same user account.
To resolve this error, you can try increasing the value of the MAX_UPDATES_PER_HOUR system variable, which sets the maximum number of updates allowed per user per hour. Alternatively, you can optimize your application to reduce the number of unnecessary updates and ensure that updates are properly optimized.
Error 1118 – Row size too large
This issue is caused by InnoDB having reached the maximum row size and cannot store more data. There are several solutions for this error. Please read this article that explains all the steps in detail.