MySQL behaves inconsistently

I need to modify stored procedure that I created myself, and I get this error using MySQL Workbench on Windows:

Error Code 1227 Acees Denied; you need the SUPER priviledge for this operation.

I can do this with no problem from a UNIX machine.  Any idea?
rudy201Asked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Kevin CrossConnect With a Mentor Chief Technology OfficerCommented:
Sorry for the extra e-mail. Another possible cause along same line is if you set the DEFINER (I tend not to), that connecting remotely with same user may still result in error if the connection is not being interpreted as the exact same scope, i.e., if defined as 'you'@'localhost'; 'you'@'windows PC' is a totally different person. This was mentioned with SSH and shared hosting environment, but might be worth looking at. I am having no difficulties on my Windows machine with MySQL; however, I do not create my procedures with DEFINER specified typically as I am typing query directly versus using a GUI and so that is more keystrokes. *smile*

Reference: http://www.hostingrails.com/MySQL-Error-1227-Access-Denied-you-need-SUPER-privilege-for-this-operation
0
 
Kevin CrossChief Technology OfficerCommented:
What credentials are you using to connect with through MySQL Workbench and is that set to proper permissions? i.e., is it possible permissions are accidentally set allowing some operations, but not others.

Here is a reference on the individual permissions:
http://dev.mysql.com/doc/refman/5.5/en/privileges-provided.html

If these were recently changed, you may simply need to run FLUSH PRIVILEGES and try again.
0
 
rudy201Author Commented:
It is the same MySQL account as what I use on UNIX.  Does MySQL Workbench do anything special with permissions that would cause error above? I can't see any evidence pointing to this from its GUI.
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Kevin CrossChief Technology OfficerCommented:
Where is the physical MySQL server located? i.e., is it Windows or MySQL. When you say the same account, it makes me think we are talking about querying the same exact MySQL server just once from a UNIX client and other from a Windows one, is that right?

My initial read was you previously had MySQL server setup on UNIX and now you have it on Windows and it is behaving differently. Operating System login and privileges are not the same as MySQL privileges; therefore, I was curious if that was the root cause.

If on the other hand, it is something in the stored procedure that making a call to underlying file system and it is literal meaning UNIX SUPER user, then may need to look at the actual stored procedure code to find your issue. I have not seen that, but then again I am not a heavy UNIX user. If the MySQL server is hosted on the same UNIX box that this works on, maybe the user there has su privileges and so whatever process the procedure invokes has rights it needs versus coming from Windows it does not. I would not think that would matter as it would run as whatever account is running the MySQL daemon, but again I am not anywhere close to an UNIX Expert.
0
 
Kevin CrossChief Technology OfficerCommented:
Okay, here is a reference that supports my original question on credentials.
http://mark.koli.ch/2010/05/mysql-triggers-and-super-privileges-access-denied-you-need-the-super-privilege-for-this-operation.html

I am pretty sure that is what we are dealing with her, but the UNIX bit is throwing me off since SUPER user means something there also. :) I would stay in the MySQL realm, though, and recheck the permissions. Or better yet, reapply them since this worked at one point.
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
I've requested that this question be deleted for the following reason:

This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
 
rudy201Author Commented:
I will close it myself.
0
 
rudy201Author Commented:
it was because of the DEFINER
0
All Courses

From novice to tech pro — start learning today.