From: "Steven Levine" <ecs-isp@2rosenthals.com>
Message-ID: <64d3cf2d.8.mr2ice.fgrirsq@earthlink.net>
Date: Wed, 09 Aug 2023 10:38:53 -0700
To: "eCS ISP Mailing List" <ecs-isp@2rosenthals.com>
In-Reply-To: <list-7611409@2rosenthals.com>
Subject: Re: [eCS-ISP] mysql upgrade 5.1.73 -> 5.6.51
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

In <list-7611409@2rosenthals.com>, on 08/09/23
   at 07:32 PM, "Paul Smedley" <ecs-isp@2rosenthals.com> said:

Hi there,

>My process was to copy the data\* directory from mysql51 to my mysql56 
>test directory,=A0 then run mysql_upgrade.

That's the recommended method and that's what I tried first.  As I
described the upgrade complained and mysqld trapped.

I have to suspect there are differences in our data.  Odd, but not
entirely unexpected.

The good news is I have developed a workaround that, at least for me, get=
s
past the traps and results in a working upgraded database.  I'll post the=

writeup later.

>mysqld now starts without warnings - so I figure it did what it needed 
>to do...

If the ungrade runs to completion it rewrites mysql_upgrade_info in the
root of the data directory tree.  Mine now says 5.6.51.

Steven

-- 
----------------------------------------------------------------------
"Steven Levine" <steve53@earthlink.net>  Warp/DIY/BlueLion etc.
www.scoug.com www.arcanoae.com www.warpcave.com
----------------------------------------------------------------------