Difference between revisions of "How to enable Show Engine Innodb Status"
From Brian Nelson Ramblings
(Created page with "==How to enable Show Engine Innodb Status== Are you trying to see the latest deadlocks or foreign key errors but run in to the following error: [Error Code: 1227, SQL State:...") |
(→How to enable Show Engine Innodb Status) |
||
Line 7: | Line 7: | ||
When this happens you will need to grant your user the PROCESS privilege. | When this happens you will need to grant your user the PROCESS privilege. | ||
− | GRANT SELECT, PROCESS ON *.* TO 'youruser'@'localhost'; | + | GRANT SELECT, PROCESS ON *.* TO '<youruser>'@'localhost'; |
===Creating a new user to view Show Engine Innodb Status=== | ===Creating a new user to view Show Engine Innodb Status=== | ||
Line 15: | Line 15: | ||
Here are the standard commands to create and grant them the privileges: | Here are the standard commands to create and grant them the privileges: | ||
− | CREATE USER '< | + | CREATE USER '<newuser>'@'%' IDENTIFIED BY '<password>'; |
− | GRANT SELECT, PROCESS ON *.* TO '< | + | GRANT SELECT, PROCESS ON *.* TO '<newuser>'@'%'; |
FLUSH PRIVILEGES; | FLUSH PRIVILEGES; | ||
This is the bare minimum to enable them to run (Show Engine Innodb Status) | This is the bare minimum to enable them to run (Show Engine Innodb Status) |
Latest revision as of 03:55, 25 February 2022
How to enable Show Engine Innodb Status
Are you trying to see the latest deadlocks or foreign key errors but run in to the following error:
[Error Code: 1227, SQL State: 42000] Access denied; you need (at least one of) the PROCESS privilege(s) for this operation
When this happens you will need to grant your user the PROCESS privilege.
GRANT SELECT, PROCESS ON *.* TO '<youruser>'@'localhost';
Creating a new user to view Show Engine Innodb Status
Sometimes you find that a client or yourself wants to view Show Engine Innodb Status and they want a new user to do this with.
Here are the standard commands to create and grant them the privileges:
CREATE USER '<newuser>'@'%' IDENTIFIED BY '<password>'; GRANT SELECT, PROCESS ON *.* TO '<newuser>'@'%'; FLUSH PRIVILEGES;
This is the bare minimum to enable them to run (Show Engine Innodb Status)