Comments on: Replication fail with “There is no ‘username’@’host’ registered” http://openquery.com/blog/replication-fail-usernamehost-registered About MySQL, Drizzle, MariaDB and more! Wed, 13 Jan 2010 12:40:20 +0000 http://wordpress.org/?v=2.8 hourly 1 By: Sheeri K. Cabral http://openquery.com/blog/replication-fail-usernamehost-registered/comment-page-1#comment-1563 Sheeri K. Cabral Mon, 29 Jun 2009 18:37:46 +0000 http://openquery.com/blog/?p=822#comment-1563 ah yes, but it would be very nice to know that the error came because of a trigger firing, and perhaps the name of the trigger! In the future, though, I've found that it's a good idea to query the INFORMATION_SCHEMA before changing users just in case this sort of thing comes up. And if/when this sort of thing does come up, query the INFORMATION_SCHEMA to see what triggers and/or stored routines might be using that username@host. If you haven't already, it would be a good idea to check the list of username@host that are in the tables for triggers and stored routines, so that you can ensure the user isn't used anywhere else, in a more obscure place. ah yes, but it would be very nice to know that the error came because of a trigger firing, and perhaps the name of the trigger!

In the future, though, I’ve found that it’s a good idea to query the INFORMATION_SCHEMA before changing users just in case this sort of thing comes up. And if/when this sort of thing does come up, query the INFORMATION_SCHEMA to see what triggers and/or stored routines might be using that username@host.

If you haven’t already, it would be a good idea to check the list of username@host that are in the tables for triggers and stored routines, so that you can ensure the user isn’t used anywhere else, in a more obscure place.

]]>