Quick Tip: Granting Access to Meta-Data on MySQL

Ever seen this exception in your log files when working with MySQL as your database back-end?

User does not have access to metadata required to determine storedprocedure parameter types. If rights can not be granted, configureconnection with "noAccessToProcedureBodies=true" to have drivergenerate parameters that represent INOUT strings irregardless of actualparameter types.

Well, I have come across this now a couple of times and for some reasonI just cannot remember how to either configure the connection to usethe "noAccessToProcedureBodies=true"switch or what the exact SQL is that I need to execute to give the userthe appropriate access. This time however I decided it is time that Iplace this information somewhere I can easily find it again and whereit can potentially also help out others. Believe me to find thesolution to this via Google searches takes a while... So, I naturallythought of the DZone network and the SQL zone in particular. Enoughtalk then, below follows the solutions for both scenarios. For thesecond one however, you will need a version of the Connector/J equal toor above version 5.0.3.

If you have root access to your MySQL database then you can simply run a query on the database to resolve the problem. What the query will do is give the specified user the needed rights on the mysql.proc table. This takes the form of the following GRANT SQL query:

GRANT [SELECT, INSERT, UPDATE] ON `mysql`.`proc` TO 'myuser'@'myhost';

That's it, after running this query on the database the above exceptiongoes away. If however, you do not have the needed root access to runthis query on the database then below is the connection string to useto get around this problem. Very simple, just add &noAccessToProcedureBodies=true to your current connection string and you are done.

String connectionURL = "jdbc:mysql://localhost:3306/mydatabase?user=myuser&password=mypassword&noAccessToProcedureBodies=true"

I sincerely hope this tip will help out someone else. If not, well,then at least I now know where to go the next time I run into thisproblem :)