1. wulfgen
  2. MAMP - Troubleshooting
  3. Tuesday, 13 August 2019
First a little history of the problem Im in - Im on a Mac....
I use MampPro to setup my sites on the local server... all well and good. So, every time I fire it up I get the upgrade nag... so, I figure its time, and hit the upgrade... and it does its thing.
 
BOOM, every database I had there - gone! GRR! Dang! - Fortunately I was proactive and copied all of the previously ( the DB dir Mamp ). The internet tells me to simply put them back in the dir and restart - which I do....
 
Now PhpMyAdmin "sees" the DB's but does not have index's for any of them - I can see the column structure, but they have this yellow/red error for anything I try to open.
 
Here's an image of what its doing -- https://i.stack.imgur.com/xi3yM.png
 
Out of all the posted info on this - the stuff I see here ( https://becomethesolution.com/innodb-error-table-mysql-innodb-table-stats-not-found ) seems to be the most intelligent.
However, not being an sql person makes it hard for me to follow correctly, and I'm afraid of screwing up the current sql that in working now ( you understand :) )
 
Do you know how to repair this - all my work is gone... I mean literally, everything!
 
Maybe there's some form of sql insert that will look at the columns and add the table index - I don't know SQL is not my baliwyck


Accepted Answer Pending Moderation
0
Votes
Undo

Ok, so I haven't done the latest upgrade just yet but it did include a MySQL upgrade version. Did you run the upgrade script included in MAMP after the upgrade? In the past, MAMP doesn't tell you to do this as part of the upgrade but you need to

 

Located here: /Applications/MAMP/bin/upgradeMysql.sh

Accepted Answer Pending Moderation
0
Votes
Undo

Yes I did that - and i didnt buy the latest upgrade - during this - I got quite flustered and abandonded the cart - so its back at 4.5 and running but the previous DBs are still showing that error

 

Even though I ran the update DB (in both cases) on them all and got back an error i can post if required....

 

I'm really only worried about two of them - the others - well, I'll just have to redo them..... :(

 

A thought just occurred - if you have a working version - and its "updates" db's - why dont I zip up the dbs Im concerned with and forward them to you - you add them to your dbs - run the update to see if that "fixes" them.

 

If it does then there are two things that could work - export a dump that i can import or send em back and i can see if my sql "sees" them - I could also do a search and replace on the naming structure to match my https://localhost/xxxxxx  name.

 

**Although I'd like to try the import sql option first though - make sense ?!?

Accepted Answer Pending Moderation
0
Votes
Undo

Just to confirm, after you did the upgrade and saw no databases and basically things were broke, did you connect to MySQL via Terminal (verify the db's were there first which I think you did) and run the upgrade script and THEN try the repair script and still you did not see any databases? The repair script is in the same directory.

 

Accepted Answer Pending Moderation
0
Votes
Undo

No i did not connect via the terminal - what I did was: I had a copy of the dbs sitting on my desktop - I placed them in the db dir in the library dir, nenamed it to v5.6 and set the orig to .BAK then restarted Mamp and went to the repair database option and, "ran it", it sees the db's but will do nothing - then in phpmyadmin, as I said before,  it sees the dbs and the columns for each one, but the index tables are simply not there.

So, I set the DB back to what it was and then copied a single DB (of mine) into the active db dir, mamp "sees it" cannot repair it, same thing......

At the moment I still have this version running - and dont intend to do any more "fiddling" with it as its working - all I'm hoping to do is get the index tables back into 2 dbs of wotk

Accepted Answer Pending Moderation
0
Votes
Undo

Ok, how about trying to rebuild the indexes on those 2 DB's then?

Accepted Answer Pending Moderation
0
Votes
Undo

I did that but it still reports the same thing

- this is why I asked about a different version being used on them to see if that works - and if so, export a dump that can be reimported.....

Mentioned above....

Accepted Answer Pending Moderation
1
Votes
Undo

Time is tick, tick, ticking for me here - are you able to assist, in any measure?

 

Hello? 2 days later?

Accepted Answer Pending Moderation
0
Votes
Undo

Sorry, have been away for a bit.

I'll leave it for others to suggest things, but if you can't go back to the old install MAMP made a backup for you during the initial upgrade, which included backups of all your databases by default (I can't tell if you moved the databases out there already which you should not have done) can you try to restore your sites if you made backups of them that way?

Accepted Answer Pending Moderation
0
Votes
Undo

Well, it looks like they are gone - I did move them out as I reinstalled the app and started from zero ..... ( 4.6.5 )

I figured I could get someone to copy what I have into their DBs and run the update using their new version to reset the indexes, then exporting a sql dump file I could import into my ( lesser ) version

  • Page :
  • 1


There are no replies made for this post yet.
Be one of the first to reply to this post!