running mysql_fix_privilege_tables kills my root password - mysql

I am learning mysql and ran into a problem with 'mysql.proc' missing when trying to create a stored procedure. mysql version 5.1.41.
I read that running the script 'mysql_fix_privilege_tables' is supposed to fix the previous error. I am getting a strange side effect... my root password is no longer good anymore when I run this script and can no longer log into mysql because of this. the only solution is to remove mysql and start over. I have done this twice now and have no clue as to why it is affecting my root password. any clues?
Updated 11/28: I found it is a bug in workbench with a particular model sync setting. It is removing the mysql database and for some reason when you do a repair, mysql erases all users. Kind of a perfect storm kind of thing I think.

Maybe this article (geared at Debian Linux running mysql) might help you and save you the pain in having to remove mysql and reinstall again. The principal should remain the same as I have noticed this is tagged with macosx.
Hope this helps,
Best regards,
Tom.

Related

How do I restart a MySQL local instance in MySQL workbench?

I've recently gotten into databases for a class I'm currently in, and I need a little bit of help. I've managed to create a database, and even populate a table with data which I was then able to grab from a node.js project I've made in Atom. Wonderful! When I went to shut it down, all seemed normal but now it won't restart. As in, when I'm in the homepage section of MySQL I double click the local instance I made(I can only assume this is opening the connection to the local instance where my database is stored) but it won't start up. I don't know what I'm doing wrong. Here is an image of the error I'm getting. I can only assume it's because the actual server isn't on but I don't know how to turn it on.
Any help is much appreciated!
Thank you!
As according to the users ikiK, P.Salmon, and Y4glory the issue I was having was that I wasn't actually turning on the server. I was able to do so by going through my Window's Services application, finding the MySQL server and starting it there instead of trying to do so through the workbench.
Once again, thank you to those who commented as that was really helpful!!
I have tried every other way mentioned here and other related posts, but it did not solve my problem, the service just wont start, but the below approach with the mysql-installer did.
For this to work you need to have your installer which you have used earlier to install MySql.
Start your windows mysql installer. For me it was "mysql-installer-community-8.0.20.0"
Then remove/uninstall the SQL Server and remove all configurations
Manually delete the SQL Server folder from "C:\Program Files\MySQL\MySQL Server 8.0."
Start your mysql installer again and install the SQL Server again
You can check now that the MySqL Server has started.
Hope it helps someone.

Sys_schema in MySQL Workbench missing after clean reinstallation

I've installed MySQL Workbench on my Macbook, but I have some problems with running scripts and creating databases, so I had to reinstall it. After reinstalling this Workbench, I found out that I am missing sys_schema in my schemas, which should be default there.
Do you know maybe how to install it there, or add it there? Cause now, I can't do anything. If I'm trying to run script, or something it's not working.
Thanks in advance!
Peter
It could be an issue that the schema is still there but the user that you use to connect to MySQL in Workbench lacks the rights to see it.
http://dev.mysql.com/doc/refman/5.7/en/sys-schema.html

MySQL password not taking after new account creation

I'm running MySQL 5.5 on Ubuntu Linux 12.04. I set MySQL up with a root user and two accounts to access the db with using Workbench. The root user works just fine and I can use it to access the DB from Workbench and other programs (like RapidAnalytics), but when I try and access the DB with my other two accounts it will recognize the user, but it won't recognize the password. I know I've entered them correctly, I've reset them a few times, I'm 99.99% certain I'm putting the right password in. On top of that, I've set up both users as DBAs, it made no difference. I made sure they had schema privledges, still nothing (though I may have done that last one wrong. I Just went into the users panel in Workbench and used the wizard they had there...)
I set a MySQL DB up on Windows 7 in the last few days, and that one works just fine. I'm quite certain I followed the same procedure...
At any rate, I have two questions.
Firstly, I read on another thread that this happens sometimes when more than one version of MySQL is installed on Linux. But I'm kind of new to Linux and I'm not sure how to figure out if I have more than one version installed. Can someone please advise if that is a good theory and if so, how to go about checking for what I have installed?
Secondly, well, I'm really just out of ideas. If someone could point me in a good direction...I'm just not sure what to ask Google anymore.

Can't access MySQL databases after upgrade to Mountain Lion (using MAMP)

I recently upgraded to Mountain Lion from Snow Leopard, and in doing so threw my entire local development environment into disarray. I solved the majority of my issues by finally installing MAMP Pro (I was previously using the "native" methods provided by Apple). The problem I have now is I still can't access my old mysql databases. I can view the "new" databases via phpmyadmin in MAMP, but I have old projects that I'd like to work on.
My old databases still exist in /usr/local/mysql/data, but they don't appear in phpmyadmin or even if I query via Terminal (after logging in to mysql & using the show databases; command). I'm sure the answer involves just a few simple commands, but I'm mainly a front-end guy, and I can't for the life of me find the solution on the internets.
Thanks.
UPDATE:
Just a reference for anyone else who might have this issue (or something similar). In order to do the dump, I ended up having to turn off MAMP's instance of MySQL, and starting up the old version (through System Preferences). Otherwise I was getting 1049 errors ("unknown database"), I suppose since it was looking at the new databases instead? Really out of my element here, if you can't tell...
Either way, now it looks like it actually doesn't matter if the MAMP version is active or not. Maybe I just needed to restart all instances of MySQL? Seriously, no clue, but all is good now...
Try this in terminal to dump old databases (replacing [text]):
/usr/local/mysql/bin/mysqldump -u root -p[pass] [db] > [filename].sql
Once you have the sql file you can import it back in with PHPMyAdmin within MAMP.

how to find the connection string details for mysql in IIS?

I installed php and mysql on my IIS 7,
Now, I can see the phpinfo() and it all works great, except, I dont know where and what are the connection string details are for mysql.
I am trying to install wordpress (via web platform installer on IIS) and everytime I try to install it, it asks for database details - I understand why its doing that, except, I dont know what they are myself.
After a lot of googling and searching, I am surprised that there are literally NO information on how to do this, no tutorials anywhere, not even bugs on this. Either that, or I'm barking up a different solar system.
Any links to tutorials on how to do this would be very helpful. But most importantly, how do I find the details about mysql?
thanks.
Do yourself a favor and download a proper GUI for working with MySQL, such as SQLYog or something similar and forget that poo of PHPMyAdmin. As mentioned, your username is most likely root without password.
You can search for a program called mysqlinstanceconfig.exe (or something similar, you should have it in your MySQL installation folder) - it allows you to quickly reconfigure your instance and you can reset your login credidentials with it.
About MySQL GUI-s: if I'm not mistaken, there's one free coming directly from MySQL but I'm not sure about that. Forget about PHPMyAdmin, it's the worst piece of code ever written and a HUGE security hole.
As you're running a MySQL server locally, your hostname would be localhost, and you can use root as the username, and put nothing as the password.