Bug #9934 DROP USER fails if mysql.procs_priv doesn't exists
Submitted: 15 Apr 2005 15:25 Modified: 17 Jan 2006 21:47
Reporter: MySQL-Front Team Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Security: Privileges Severity:S4 (Feature request)
Version:5.0.3-beta OS:Microsoft Windows (Windows XP)
Assigned to: CPU Architecture:Any
Triage: Triaged: D5 (Feature request)

[15 Apr 2005 15:25] MySQL-Front Team
Description:
If the table mysql.procs_priv the DROP USER query fails.

How to repeat:
CREATE USER TestUser;
DROP TABLE mysql.procs_priv;
DROP USER TestUser;
[15 Apr 2005 16:04] Miguel Solorzano
Sorry I don't understand well what you meant, below the current
behavior:

c:\mysql\bin>mysql -uroot
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1 to server version: 5.0.5-beta-debug

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> use test;
Database changed
mysql> CREATE USER TestUser;
Query OK, 0 rows affected (0.06 sec)

mysql> DROP TABLE mysql.procs_priv;
Query OK, 0 rows affected (0.06 sec)

mysql> DROP USER TestUser;
ERROR 1146 (42S02): Table 'mysql.procs_priv' doesn't exist
mysql>
[8 Nov 2005 14:13] MySQL-Front Team
The developers are not interessed about our bug messages.
[17 Jan 2006 21:24] MySQL-Front Team
MySQL is not interessed to fix this bug.

We know this from a lot of other critcal bugs. :-(
[5 May 2006 18:52] Quinn Comendant
I had this problem but was able to fix it by running mysql_upgrade.
[10 Feb 2007 1:12] Nick Darlow
With mysql  Ver 14.12 Distrib 5.0.26 I found you can work around this as follows

mysql> use mysql;

mysql> create table procs_priv ( test int );
Query OK, 0 rows affected (0.07 sec)

mysql> drop user 'nick'@'localhost';
Query OK, 0 rows affected (0.00 sec)

mysql> drop table procs_priv;
Query OK, 0 rows affected (0.00 sec)
[14 Oct 2007 14:17] Jerome Perrin
If you encounter this after an update, run mysql_upgrade_shell command: it will create the missing table.
[29 Dec 2008 5:46] Nilesh Patil
I faced this problem when i was upgrading from mysql 4.0 to mysql 5.1. I resolved this by running, 'mysql_fix_privilege_tables'. 

- nilesh