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

  - Open session with current directory set to 5.6 bin directory
    Run binaries from the directory

  - Verify my.cnf is 5.6 compatible
    Edit as needed to protect/hide 5.1 data

  - 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
  - Run
      mysql_upgrade
    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

very good, thank you

what was making exiting my mysql --console

  ;innodb_buffer_pool_size = 512M

after commenting it the console started

i copied all the data from 5.1, than mysqlD started and got running

using mysql_upgrade --force -u myuser -pmypwd i got the upgrade running and it completed (after a crash/exit of mysqld that i had to restart)

but mysqlD show a lot of warnings like these:

2023-08-10 10:50:32 3234 [Warning] InnoDB: Cannot open table rcube2/session from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.

2023-08-10 10:50:32 3234 [Warning] InnoDB: Cannot open table rcube2/system from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.


about the innodb buffer pool size this could give performance issues?

thanks

massimo