I am having an issue in MySQL Workbench, where many of my created schemas are missing. I was in a Coding Bootcamp, and all the schemas that I created during that period vanished. The ones created beforehand are all still there. I'm pretty sure I am using the same user account and I checked the privileges. I also checked usr/local/var/mysql and the missing schemas are not located in this folder. So my question is what happened to them? I certainly did not delete them. Maybe someone else did when I wasn't looking? Or could this have been caused by an update? I went several months without opening Workbench, so I'm not exactly sure when this happened. I have searched for hours and hours on SO and google and have not found an answer. Any ideas are much appreciated!
Also, I am on MacOS Catalina 10.15.7 if that helps.
Related
I know #1146 has been asked too many times, but my case is a bit different, so please bear with me.
I was trying to delete a database "libdb_bak" as I no longer need the backup db, however, some error happened and PHPMyadmin asked me to create something related to "pma" thing - I didn't paid attention to the details, and after confirming the operation, I go on to my other tasks.
After returning to PHPMyAdmin, the operation seems failed, so I go to C:\AppServ\MySQL\data\ to delete the database manually, now every time I tried to go into any database, it will fail with error message regarding "libdb_bak.pma_tracking" doesn't exists.
I tried uninstalling AppServ (AppServ: 8.6.0 includes MySQL:5.7.17, PHPMyAdmin: 4.6.6) and deleted the whole AppServ directory (clean delete, nothing left in Recycle Bin), restart PC, re-install AppServ, and the problem still exists - it is still looking for the libdb_bak.pma_tracking file, which, it is not supposed to remember, since I already done a clean wipe and fresh re-install.
Can anyone help me to locate the residue of this file location memory, so that I can get rid of it for good? I can't use my PC to continue my work, as long as this problem still exists. Thanks in advance.
Have you tried this one: #1146 - Table 'phpmyadmin.pma_recent' doesn't exist
Btw, Have you tried creating table "libdb_bak" from the terminal or Work Bench/Heidisql etc? And see if recreating the data files solves the issue.
Solved the problem, the culprit is the cookies! Cleared my browser history for the last few hours and the problem goes away.
Thanks to Batman's answer, recreating db with the same error leads me to investigate other options and found the solution! Thanks.
I have little experience with MySQL Workbench and need some helps to figure out an issue. I loaded a new EER diagram from a .MWB file in the GUI and was trying to convert it into the SQL with Forward engineer. Initially, I was connected to the localhost and when, I press the Forward engineer..., nothing happens. The figure is as following, I'm working in the Mac OS Sierra operating system.
What I am missing here ? Some advice will help from the more expert users.
I use MySQL Workbench 6.3version for the work,
I've had this same issue with the latest release of MySQL Workbench (macOS). It's definitely some bug as previously, I didn't have any issues forward engineering.
Here's a workaround:
Normally, you'd go to:
Database > Forward Engineer...
To work around this bug, instead go to:
Database > Synchronize Model...
This will look for any open ERDs which do not currently exist with the rest of your schemas, and will allow you to forward engineer the schema that way.
Warning: This could get hairy if you had a lot of ERDs opened and didn't want to synch all of them, so make sure you've got the right ones checked!
I know this is a late answer, but this solution allowed me to forward engineer an ERD which previously was not firing (just as you described, nothing from MySQL Workbench).
I found your post when trying to find a solution, and while troubleshooting, heard via a personal anecdote about this work around. It may already be posted elsewhere on stack (tried to find link but couldn't find it), but hope this helps :)
Try:
File > Export > Forward Engineer SQL CREATE script
I have been dealing with this issue for a while now. For some reason, when i went to run a Ubuntu upgrade, MySql-server upgrade failed. This was on about 8/10. This had happened before due to a "DATADIR" link (won't go into detail on that just now). I went through hell trying to get the package to upgrade and eventually got the package to upgrade by creating a new MySql database structure (after moving mine somewhere else). Once I did that (with some steps involved) the package upgrade completed.
Then, when I tried to replace the "new" databases with my old onse, it wouldn't start the service. I came to find out that the "Mmysql" (system) database folder was just completely gone.
So, I took the "new" database and overlayed it on my "old" database files. This got me in! Of course, old users, and anything else in the system database, was gone. So I started to rebuild them.
The problem occurred when i tried to go into some old databases. About half of them report that the table does not exist when trying to load them. Mostly, it is all of the tables in particular database, but there are a few databases where some tables "don't exist" and others do.
The thing is that the tables do exist. I believe they are simply corrupt.
So, I'm really trying here, but I can't seem to figure out how to get all of the tables to load. I have a backup from the 13th, presumably after the upgrade failed but before I really started messing with things. I'm going to try to use that, but if anyone knows how/why some tables are corrupted all of a sudden and why others are not and especially if someone knows how to fix this, that would be absolutely wonderful.
Unfortunately, my regular backups haven't been working for months, and the latest backup I currently have access to is 2 years old. Quite a bit has changed in the database since then, but as a last ditch effort, I may try to import that data and use "mysql_upgrade" to restore this, then overlay any new databases I have created since then into the directory structure and see if they import that way.
Thanks for any suggestions you may offer.
--mobrien
I believe this was due to a permissions issue that had some files locked and when I fixed the perm issue, the tables that were accessible were corrupted. I restored the same backup again and this time it worked. The only folder that was missing was the "mysql" folder, and for that I recreated a new one, then patched it in, then created new user permissions for the existing tables. This was working, but then I ran into another issue, so I will open a new questions for that. This has been a nightmare and the moral of the story is: keep better backups and test them!
I want to create database in phpMyAdmin. I have done these many times before in my old system and old phpMyAdmin version, but currently not able to do it. And tried to search this problem through a lot of question,but couldn't find the answers.
Because Most of them have problem of privilege, but i think i don't have this problem because i have all the privileges.
When i am trying to create database, it doesn't give any error but it just displays "Processing Request".
I am attaching screenshot.
let me know if you can think of any reason behind this.
Any help would be appreciated.
you should try it after reinstalling phpmyadmin..
It seems you are on hosting server.
Most probably you are getting a limited number of databases on your account.
You must have exceeded the allowed no. of databases on the account.
If not please add a comment, we will see again.
Cheers!!!
Yes. I was had same problem. What i do is.. move to another browser.
Im using mozilla when i had the problem. Then when i change to using interrnet explorer. Its work perfectly. Idk, what happen but this is work...
Unfortunately, the problem is not more specific than that. I've found a few examples of people reporting similar problems by doing a Google search, but I can't find the part of the restore that is actually causing the problem, which might help me track it down on my own.
Suggestions for either resolving this problem or being able to track down the root cause would be appreciated.
There's one bug logged at bugs.mysql.com that references the error you describe:
"Bug #37253 Unable to restore backup file containing BLOBs"
The solution described in that bug is to increase the max_allowed_packet in the MySQL server configuration. The user confirmed that raising the value to 100M allowed him to restore his database.
ANOTHER FIX
I also had this problem! The answers online didn't seem to help (max_allowed_packet and others)
Here's what fixed mine:
Instead of running the Restore function, I imported through MySQL Migration Toolkit (installed with GUI Tools on Windows).
The Migration Toolkit also failed, but had descriptive errors in the Log on the final page. In my case, it was a few incorrect Date fields in my data (usually "0000-00-00") that wouldn't migrate correctly.
Fixing these dates in my tables solved the Restore problem.
Hope this helps somebody else out there.
I have had something similar in the past- it has something to do with how it was backed up. I think some applications put invalid comments in the backup files which cause errors.
My suggestion- if you are stuck trying to restore those files- is to incrementally start backing up from sections of the backup file and find what is causing the problems- which from what I recall the case for me was that they were some text in the file that was inconsequential to remove.