Bug #48862 | show procedure status | ||
---|---|---|---|
Submitted: | 18 Nov 2009 10:58 | Modified: | 19 Mar 2010 12:37 |
Reporter: | Suresh Kuna | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Information schema | Severity: | S1 (Critical) |
Version: | 5.1.40-log MySQL Community Server (GPL) | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | show procedure status or mysqldump --routines |
[18 Nov 2009 10:58]
Suresh Kuna
[18 Nov 2009 11:04]
Valeriy Kravchuk
Thank you for the problem report. This command works for me on one of my databases: 77-52-1-11:5.1 openxs$ bin/mysql -uroot test Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 Server version: 5.1.42-debug Source distribution Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> show procedure status where db='test'; +------+-------+-----------+----------------+---------------------+---------------------+---------------+---------+----------------------+----------------------+--------------------+ | Db | Name | Type | Definer | Modified | Created | Security_type | Comment | character_set_client | collation_connection | Database Collation | +------+-------+-----------+----------------+---------------------+---------------------+---------------+---------+----------------------+----------------------+--------------------+ | test | p1 | PROCEDURE | root@localhost | 2009-11-17 13:59:11 | 2009-11-17 13:59:11 | DEFINER | | latin1 | latin1_swedish_ci | latin1_swedish_ci | | test | proc1 | PROCEDURE | root@localhost | 2009-11-16 16:11:08 | 2009-11-16 16:11:08 | DEFINER | | latin1 | latin1_swedish_ci | latin1_swedish_ci | +------+-------+-----------+----------------+---------------------+---------------------+---------------+---------+----------------------+----------------------+--------------------+ 2 rows in set (0.06 sec) So, I have two questions to clarify: 1. Is it a new installation of 5.1.40 or you had upgraded from some newer version, 5.x.y? 2. Do you have any procedures created in this database?
[18 Nov 2009 12:50]
Suresh Kuna
Hi Valeriy, There are no procedures created on the database, and the mysqld server 5.1.40 is newly installed and imported the dump taken from older version. I did a mysql_upgrade of the database and it go resolved now. Thanks Suresh Kuna
[18 Nov 2009 13:45]
Valeriy Kravchuk
Nice to know the problem is solved. These messages: 091118 3:22:15 [ERROR] Column count of mysql.db is wrong. Expected 22, found 20. The table is probably corrupted 091118 3:22:15 [ERROR] mysql.user has no `Event_priv` column at position 29 and the fact that mysql_upgrade fixed the problem proves that you had a couple of "corrupted" system tables. If they were NOT from 5.0.x you had previously in the same data directory, and if you had NOT restored entire mysql database from 5.0.x, then we have a problem in our binaries. What exact binaries you had installed? Please, provide download URL.
[19 Dec 2009 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[19 Dec 2009 13:26]
Suresh Kuna
Thanks...
[19 Dec 2009 14:00]
Valeriy Kravchuk
So, do you agree that this is not a bug?
[19 Dec 2009 15:13]
Suresh Kuna
Yep Valeriy Kravchuk. Thanks Suresh Kuna
[19 Mar 2010 12:37]
MySQL Verification Team
duplicate of bug #41726