Mailing List ecs-isp@2rosenthals.com Archived Message #1078 | tilbake listen |
|
---|
Il 10/08/2023 00:19, Steven Levine ha scritto:
In <list-7611426@2rosenthals.com>, on 08/09/23
at 12:09 PM, "Massimo S." <ecs-isp@2rosenthals.com> said:
Hi all,
Here's the mysql upgrade procedure that worked for me
==============================
== mysql_upgrade 5.1 -> 5.6 ==
==============================
- Tested with mysqld
Ver 5.1.73 for pc-os2-emx on i386 (Source distribution)
and
Ver 5.6.51 for OS2 on i386 (Source distribution)
- The following assumes
5.6 datadir will be /data/mysql56
5.1 datadir is /data/mysql51
innodb_data_home_dir is /data/mysql56-data/innodb
- Use names that match your setup
hi Steven,
i first need to try 5.6.51 and i will point some websites and webmail to the new
mysql installation, if all runs correctly i will start with this new setup
i will not upgrade mysql on the same VM/directories
i'm going to copy all the stuff from the mysql running in production to the other mysql 5.6.51 on another VM
- Open session with current directory set to 5.6 bin directory
Run binaries from the directory
- Verify my.cnf is 5.6 compatible
yes, i dit
Edit as needed to protect/hide 5.1 data
i don't need this since mysql 5.1 is on another vm
- Create /data/mysql56
- Create /data/mysql56/mysql
- Create /data/mysql56/innodb
- Copy /data/mysql51/mysql to /data/mysql56/mysql
- Run
mysqld --console
The server should start
There will be warnings
done, yes, i've warnings :)
- Run
mysql_upgrade
a couple of crash, but after it completed with OK
The server may crash
- If the server crashes, run
mysqld --console
to restart the server
There will be warnings
Run
mysql_upgrade
to retry the upgrade
The upgrade should run without errors
if not get help
- Copy the rest of the 5.1 databases to /data/mysql56
- Run
mysql_upgrade --force
to upgrade these databases
The upgrade should run without errors
If not get help
- Run
mysqlcheck --all-databases
to cross-check upgrade results
- Check /data/mysql56/mysql_upgrade_info
It should contain 5.6.51
The logs imply that, at least in my case, only the mysql database needed
unusual modifications. The log output for all the other databases and
tables reported OK with no additional messages or warnings.
Steven
here i've issue, eg. with roundcube webmail
2024-12-10 13:49:15 5311 [Warning] InnoDB: Cannot open table rcube2/session from
the internal data dictionary of InnoDB though the .frm file for the table exist
s. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for ho
w you can resolve the problem.
i don't understand if i've to copy also innodb stuff from 5.1 vm to 5.6 vm
or if i have to let mysql 5.6 recreate it
please help me ;)
i need to upgrade to 5.6, 5.1.73 is too much old and i've issues
importing new websites or managing DB with phpmyadmin
massimo
Abboner: Feed,
Digest,
Index. Stopp abbonement E-post til ListMaster |