Today’s company’s project view query reported an error. Find the reason for the code and view, and find that there is no problem, and the view will make an error. Errors are reported as follows:
ERROR 1615 (HY000): Prepared statement needs to be re-prepared
Many cases are caused by unreasonable setting of MySQL variable values. Adjust the following values:
table_ open_ cache 64=16384
table_ definition_ cache 256=16384
mysql set global table_ open_ cache=16384;
mysql set global table_ definition_ cache=16384;
Error 1615 (HY000): prepared statement needs to be re prepared occurs suddenly in a stored procedure that can normally run
It may be caused by unreasonable MySQL configuration parameters. The solutions are as follows
SHOW VARIABLES LIKE ‘%table_ open_ cache%’;
Variable_ name Value
table_ open_ cache two thousand
table_ open_ cache_ instances one
SHOW VARIABLES LIKE ‘%table_ definition_ cache%’;
Variable_ name Value
table_ definition_ cache four thousand
adjust variable value
— table_ open_ cache
SET GLOBAL table_ open_ cache=16384;
SET GLOBAL table_ definition_ cache=16384;
Similar Posts:
- Prepared statement needs to be re prepared
- The ‘INFORMATION_SCHEMA.GLOBAL_STATUS’ feature is disabled; see the documentation for …
- [Solved] MYSQL Error 1040 (HY000): too many connections
- Loading local data is disabled; this must be enabled on both the client and server sides
- How to Solve MySQL Secure file priv error
- How to Solve Mysql Error 1206: The total number of locks exceeds the lock table size
- ERROR 2006 (HY000): MySQL server has gone away No
- [Solved] MYSQL5.6 Error: ERROR 1709 (HY000): Index column size too large. The maximum column size is 767 bytes.
- MySQL Error: [Err] 1071 – Specified key was too long; max key length is 767 bytes
- The solution of the table is full in MySQL