Page 1 of 1

Upgrade 1.7.x to 1.8.x - tables DB crash!

PostPosted: 19. July 2013 18:30
by tab
Hi,
I upgraded my old version of xampp (1.7.2) to the last stable version (1.8.2).
I had previously made ​​a backup of
- htdocs
- mysql/data/
Now, many of the DBs in phpmyadmin are without tables. Why?

Re: Upgrade 1.7.x to 1.8.x - tables DB crash!

PostPosted: 19. July 2013 22:02
by hackattack142
Hello,

Depending on the storage engine you are using, you cannot just copy the files over.

If you still have the old folder, I recommend exporting your databases to a SQL file and reimporting them in the new version.

Re: Upgrade 1.7.x to 1.8.x - tables DB crash!

PostPosted: 22. July 2013 14:05
by tab
Hello,
is there a way to export each database in only one SQL command?

Re: Upgrade 1.7.x to 1.8.x - tables DB crash!

PostPosted: 23. July 2013 01:54
by hackattack142
Yes, you can use the command line mysqldump program in the '/xampp/mysql/bin' folder.

You could script it to do something like
Code: Select all
mysqldump -uroot -ppassword dbname > dbname.sql

if you have a password set. If your root password is still blank, you can do
Code: Select all
mysqldump -uroot  dbname > dbname.sql

This will not add drop/create database statements to the dump. You should consult the many export options to enable that stuff.

There are many export options. You can do
Code: Select all
mysqldump --help
for more information.

Re: Upgrade 1.7.x to 1.8.x - tables DB crash!

PostPosted: 02. October 2013 08:42
by MarjWyatt
I am running Xampp 1.7.3 on my Windows XP Laptop. I have nearly 100 active development projects within my installation and want to make sure that I'm understanding what is needed to upgrade to the latest stable version of Xampp.

I have read this thread> http://community.apachefriends.org/f/viewtopic.php?f=16&t=50988

Backing up essential files and configurations seems pretty straightforward but, for what ought to be obvious reasons, I want to ensure that I don't create a whole lot of unnecessary work for myself with this upgrade. The last time I did this, it didn't go well.

Am I gleaning from this thread that I must export each development's database (nearly 100) and import those databases into the new environment?

Re: Upgrade 1.7.x to 1.8.x - tables DB crash!

PostPosted: 02. October 2013 10:03
by Altrea
MarjWyatt wrote:want to make sure that I'm understanding what is needed to upgrade to the latest stable version of Xampp.

Is an upgrade really neccessary? Not always is newer equals better.

MarjWyatt wrote:I have read this thread> viewtopic.php?f=16&t=50988

Backing up essential files and configurations seems pretty straightforward but, for what ought to be obvious reasons, I want to ensure that I don't create a whole lot of unnecessary work for myself with this upgrade

This thread is a best practice to prevent known issues. You don't have to follow all steps if you don't want to. It's your system.

MarjWyatt wrote:Am I gleaning from this thread that I must export each development's database (nearly 100) and import those databases into the new environment?

Clean exports of databases (especially for InnoDB Databases) are always highly recommend, at best with the mysql included tool mysqldump.
saving and recopying the mysql data folder CAN work, but not in all cases.

At the end: more backups are always more backups are always more backups ...

Re: Upgrade 1.7.x to 1.8.x - tables DB crash!

PostPosted: 05. October 2013 08:22
by MarjWyatt
My reason for wanting to upgrade is primarily because i would like a newer version of PHP (5.4) so my development is aligned with my hosting services.

@Altrea ... you wrote :
"This thread is a best practice to prevent known issues. You don't have to follow all steps if you don't want to. It's your system."

I understand that I don't have to follow all steps and that it is my system. What I was trying to understand and apparently asked poorly if this was THE method for upgrading.

Is there a way to export the entire set of databases in local host with one command rather than exporting each database individually?

Thanks for your previous reply and thank you, in advance, to anyone who responds in the future.

Re: Upgrade 1.7.x to 1.8.x - tables DB crash!

PostPosted: 05. October 2013 09:47
by Altrea
Hi MarjWyatt,

MarjWyatt wrote:What I was trying to understand and apparently asked poorly if this was THE method for upgrading.

What answer do you expect now? There is NO ultimate outstanding upgrade method to master all ever possible situations. Systems are different and you should know your system to understand what steps of a specific HowTo you don't have to follow to backup and upgrade successful.

MarjWyatt wrote:Is there a way to export the entire set of databases in local host with one command rather than exporting each database individually?

mysqldump --all-databases
Be careful with database users and passwords. You should google how to move them correctly, for example this way:
http://geroldm.com/2012/10/migrate-mysq ... nt-server/

best wishes,
Altrea

P.S.:
MarjWyatt wrote:@Altera ... you wrote :

If you can't write my name correctly please omit it or copy it. That is not the most important thing in the world, but i don't like that :D

Re: Upgrade 1.7.x to 1.8.x - tables DB crash!

PostPosted: 05. October 2013 20:58
by MarjWyatt
Apologies for mis-spelling your name. Thanks for the reply.

I'll not come back with more questions of you. Your tone is unnecessarily unpleasant. I did not like the "what do you expect now" opener.

Re: Upgrade 1.7.x to 1.8.x - tables DB crash!

PostPosted: 05. October 2013 22:17
by Altrea
MarjWyatt wrote:I'll not come back with more questions of you. Your tone is unnecessarily unpleasant. I did not like the "what do you expect now" opener.

Sorry, i didn't want to be rude. That was a serious question. And i tried to answer it as good as i can.