From: "Steven Levine" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTPS id 7630185 for ecs-isp@2rosenthals.com; Wed, 09 Aug 2023 18:30:11 -0400 Received: from secmgr-va.2rosenthals.com ([50.73.8.217]:52915 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1qTrgn-0000g0-0H for ecs-isp@2rosenthals.com; Wed, 09 Aug 2023 18:30:01 -0400 Received: from mta-101b.earthlink-vadesecure.net ([51.81.61.61]:41691 helo=mta-101a.earthlink-vadesecure.net) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1qTrgh-0002sD-0Q for ecs-isp@2rosenthals.com; Wed, 09 Aug 2023 18:29:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=iTrrI5Nx374mbsbsBoo1pvLeGUkajpx1hB0ttM yGDOc=; c=relaxed/relaxed; d=earthlink.net; h=from:reply-to:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:list-id:list-help:list-unsubscribe:list-subscribe:list-post: list-owner:list-archive; q=dns/txt; s=dk12062016; t=1691620194; x=1692224994; b=HR7KMz7Uxqy/C3XMmUN6fm5qJ/dEL5UvYE/lFG7V2ZprZpWzL6nEbSV 9srPffEnbm7ZeTaaLteKDVHYinaPvUXEALyKaKmmLKhM2+qBBXUoBLZ9v3qCWNpyiQv4Q6i UWQ9PVjPqBbMBsllhrX0iKK8RPcdtq+Kq9mWT+7OcN1hN6SJird20SAmTOY0VHps8kV3Uax gnlPnCvfJ/eOSR7NiHbqkizleA5UOsXhjkATwP8GBBMcXeHDHgw3T5VBcsGhiP02cS2wDYL SuhgosU1PkFgX4wV1Fiu7gniTFn6D7pG6DYj9DEbzFx5EnzM65aIchmOyQIUfHes+2WmXYT f5Q== Received: from slamain ([108.193.252.56]) by vsel1nmtao01p.internal.vadesecure.com with ngmta id 52f96390-1779d79aa3b072f2; Wed, 09 Aug 2023 22:29:54 +0000 Message-ID: <64d41103.12.mr2ice.fgrirsq@earthlink.net> Date: Wed, 09 Aug 2023 15:19:47 -0700 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] mysql upgrade 5.1.73 -> 5.6.51 X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 08/09/23 at 12:09 PM, "Massimo S." 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 -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------