Bug #19487 Unexpected error "Definer is not fully qualified"
Submitted: 2 May 2006 18:13 Modified: 12 Jun 2006 11:05
Reporter: Andrew Cuthbert Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server Severity:S2 (Serious)
Version:5.0.19 OS:Linux (Redhat Enterprise)
Assigned to: CPU Architecture:Any

[2 May 2006 18:13] Andrew Cuthbert
We recently launched a high profile site using MySql. The site gets around 10 million page impressions a month. The database is under constant load (on average 150 simultaneous queries). Load is fine on the server however we are getting strange errors on some queries. These have been logged by the Zend Platform but we can't understand it. A simple query such as:

SELECT * FROM tblProp WHERE PropID = 'DA1932507'

will sometimes cause a "Definer is not fully qualified" error. A google search only mentions this error in relation to triggers and replication. I do have two triggers on this table but this is just a select. And why would it happen so infrequently? The error has happened 185 times in two hours. Not that many in comparison to the overall site traffic but enough to ring alarm bells!

How to repeat:
only specific queries cause the error but it happens at random intervals.
[12 May 2006 11:05] Valeriy Kravchuk
Please, send the SHOW CREATE TABLE tblProp results. Do you have anything unusual in your error log for the periods when you got that errors?

Send you my.cnf file also.
[12 Jun 2006 23: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".