Re: MacOS Server 5 problem after upgrade

> Am 04.09.2016 um 23:35 schrieb Reindl Harald : > > > > Am 04.09.2016 um 16:17 schrieb Matthias Schmidt: >>> Am 04.09.2016 um 16:29 schrieb Reindl Harald : >>> >>> Am 04.09.2016 um 08:40 schrieb Matthias Schmidt: 2016-09-04 15:25:19 85518

Re: MacOS Server 5 problem after upgrade

Am 04.09.2016 um 16:17 schrieb Matthias Schmidt: Am 04.09.2016 um 16:29 schrieb Reindl Harald : Am 04.09.2016 um 08:40 schrieb Matthias Schmidt: 2016-09-04 15:25:19 85518 [ERROR] /usr/local/mysql/bin/mysqld: Can't create/write to file

Re: MacOS Server 5 problem after upgrade

> Am 04.09.2016 um 16:29 schrieb Reindl Harald : > > > > Am 04.09.2016 um 08:40 schrieb Matthias Schmidt: >> 2016-09-04 15:25:19 85518 [ERROR] /usr/local/mysql/bin/mysqld: Can't >> create/write to file '/usr/local/mysql/data/mysqld.local.pid' (Errcode: 102 >> -

Re: MacOS Server 5 problem after upgrade

Am 04.09.2016 um 08:40 schrieb Matthias Schmidt: 2016-09-04 15:25:19 85518 [ERROR] /usr/local/mysql/bin/mysqld: Can't create/write to file '/usr/local/mysql/data/mysqld.local.pid' (Errcode: 102 - Operation not supported on socket) 2016-09-04 15:25:19 85518 [ERROR] Can't start server: can't

MacOS Server 5 problem after upgrade

Hello, sorry if this question has been asked already - at least google din’t find a sufficient answer :( I have been upgrading a MacOS 10.6 server to serverv5, which is MacOS 10.11 I was running before: mysql-5.5.40-osx10.6-x86_64 upgrade has been always a no-brainer: download the dmg and run

Re: Upgrade from 5.5 to 5.6

need to do? Or do I not have the correct version of mysql_upgrade? surely, but why don#t you upgrade mysql-server? Yeah, that would help. All good now. Thanks. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql

Re: Upgrade from 5.5 to 5.6

you upgrade mysql-server? signature.asc Description: OpenPGP digital signature

Upgrade from 5.5 to 5.6

I am upgrading my server from 5.5 to 5.6. This is on CentOS 6.5. I removed 5.5 like this: yum remove mysql-libs MySQL-client MySQL-devel MySQL-shared and I installed 5.6 from MySQL-5.6.24-1.linux_glibc2.5.x86_64.rpm-bundle.tar with: rpm -i MySQL-client-5.6.24-1.linux_glibc2.5.x86_64.rpm

Things to be considered before/after the OS patch or upgrade

Hi all, we're going to patch our MySQL servers. Most of them are RHEL/OEL 5.x and are going to be upgraded to 5.x+n (for example 5.5 to 5.10). I don't seem to find anything about this in the official documentation (verifying the patch compatibility, relinking etc.). Any hints? Best regards

Re: Things to be considered before/after the OS patch or upgrade

Am 15.04.2014 11:22, schrieb Radoulov, Dimitre: we're going to patch our MySQL servers. Most of them are RHEL/OEL 5.x and are going to be upgraded to 5.x+n (for example 5.5 to 5.10). I don't seem to find anything about this in the official documentation (verifying the patch compatibility,

Re: Things to be considered before/after the OS patch or upgrade

to, or actually we *must*, upgrade the binaries only in case of a release upgrade (RHEL 5 to 6, for example), i.e. when a different binary distribution exsists: MySQL-5.6.17-1.rhel5.x86_64.rpm to MySQL-5.6.17-1.el6.x86_64.rpm. Best regards Dimitre -- MySQL General Mailing List For list archives: http

Re: Things to be considered before/after the OS patch or upgrade

, that's why you use RHEL or a clone at all Thank you! So I suppose we need to, or actually we *must*, upgrade the binaries only in case of a release upgrade (RHEL 5 to 6, for example), i.e. when a different binary distribution exsists: MySQL-5.6.17-1.rhel5.x86_64.rpm to MySQL-5.6.17-1.el6.x86_64

Re: Things to be considered before/after the OS patch or upgrade

at all Thank you! So I suppose we need to, or actually we *must*, upgrade the binaries only in case of a release upgrade (RHEL 5 to 6, for example), i.e. when a different binary distribution exsists: MySQL-5.6.17-1.rhel5.x86_64.rpm to MySQL-5.6.17-1.el6.x86_64.rpm el5 = RHEL5 el6 = RHEL6

Re: Things to be considered before/after the OS patch or upgrade

On 15/04/2014 12:13, Manuel Arostegui wrote: [...] Thank you! So I suppose we need to, or actually we *must*, upgrade the binaries only in case of a release upgrade (RHEL 5 to 6, for example), i.e. when a different binary distribution exsists: MySQL-5.6.17-1.rhel5.x86_64.rpm to MySQL

Re: Things to be considered before/after the OS patch or upgrade

On 15/04/2014 12:18, Reindl Harald wrote: Am 15.04.2014 12:05, schrieb Radoulov, Dimitre: [...] o ABI breakages, that's why you use RHEL or a clone at all Thank you! So I suppose we need to, or actually we *must*, upgrade the binaries only in case of a release upgrade (RHEL 5 to 6, for example

Re: Things to be considered before/after the OS patch or upgrade

- Original Message - From: Dimitre Radoulov cichomit...@gmail.com Sent: Tuesday, 15 April, 2014 12:17:54 PM for major release upgrades - 5.x to 6.x - we'll use a different hosts. I would like to point out that where MySQL is concerned, the minor versions are a major upgrade - 5.0

Re: Things to be considered before/after the OS patch or upgrade

On 15/04/2014 13:53, Martin Gainty wrote: [...] It seems that I gave a wrong impression, but we actually have a big team of sys admins :) MGhe is asking that you hire an experienced DBA MG(vs packing up your office with Einwanderer) Wow! Thank you! Putting back the list in CC for the

Re: Things to be considered before/after the OS patch or upgrade

, the minor versions are a major upgrade - 5.0-5.1, 5.1-5.5 and 5.5-5.6 are all MAJOR changes, and you would do well to go through the release notes for each version. Hi Johan, I was talking about OS upgrades: RHEL/OEL 5.x to 6.x, not MySQL. Thanks Dimitre -- MySQL General Mailing List For list

Re: Things to be considered before/after the OS patch or upgrade

is concerned, the minor versions are a major upgrade - 5.0-5.1, 5.1-5.5 and 5.5-5.6 are all MAJOR changes, and you would do well to go through the release notes for each version. he is talking about a long outstanding update of *CENTOS* from 5.5 to 5.10 which does not anything to the mysql package

Re: Things to be considered before/after the OS patch or upgrade

, thus my initial question ... and you are stating that you don't use the distribution packages of MySQL so it is not affected at all from a dist-upgrade? No, absolutely. We're using the Community and the Enterprise editions of the Oracle's MySQL distribution. Best regards Dimitre -- MySQL

5.1 to 5.6 upgrade: is it possible?

Hello, Have anybody tried to upgrade 5.1 to 5.6? I believe running mysql_upgrade should be enough, but does there are some caveats? Ilya Kazakevich.

Re: 5.1 to 5.6 upgrade: is it possible?

On 2013-12-04 1:33 PM, Ilya Kazakevich wrote: Hello, Have anybody tried to upgrade 5.1 to 5.6? I believe running mysql_upgrade should be enough, but does there are some caveats? Ilya Kazakevich. The MySQL recommendation is to upgrade one major version at a time, ie 5.1-5.5-5.6. There are so

Re: 5.1 to 5.6 upgrade: is it possible?

I would from 5.1.40 to 5.5.8 first and then to 5.6 On Dec 4, 2013, at 11:33 AM, Ilya Kazakevich kazakevichi...@gmail.com wrote: Hello, Have anybody tried to upgrade 5.1 to 5.6? I believe running mysql_upgrade should be enough, but does there are some caveats? Ilya Kazakevich. -- MySQL

Re: 5.1 to 5.6 upgrade: is it possible?

with their own set of improvements and bug fixes) since then. If anyone cannot perform a stepwise binary upgrade (...-4.1-5.0-5.5-5.6-5.7- ... ) , then dump your 5.1 data and restore it to an empty installation of your target version. (Note 5.7 is not yet GA but is available for testing and planning

Re: replication fails after upgrade to 5.6

From: Mike Franon kongfra...@gmail.com Sent: Thursday, February 21, 2013 11:43 PM To: Reindl Harald h.rei...@thelounge.net Subject: Re: replication fails after upgrade to 5.6 Unfortunately that is not possible at the moment, I have 6 slaves off the one master

Re: replication fails after upgrade to 5.6

So I created a new test box on AWS, and just did one upgrade from 5.0.96 to 5.1, like I did before and replication will not work from a master with 5.0.96 to a slave with 5.1.68 I keep getting Error 1062, Duplicate Entry for key I get no errors when I do a mysql_upgrade, all comes back ok. I

Re: replication fails after upgrade to 5.6

both should have the same version Am 21.02.2013 18:03, schrieb Mike Franon: So I created a new test box on AWS, and just did one upgrade from 5.0.96 to 5.1, like I did before and replication will not work from a master with 5.0.96 to a slave with 5.1.68 I keep getting Error 1062, Duplicate

Re: replication fails after upgrade to 5.6

Unfortunately that is not possible at the moment, I have 6 slaves off the one master, also I want to test it as much as possible before upgrading the master. Is the only way to really fix this is to upgrade master? I thought you can replicate from master - slave if version is higher on slave

Re: replication fails after upgrade to 5.6

Am 21.02.2013 19:11, schrieb Mike Franon: Is the only way to really fix this is to upgrade master? I thought you can replicate from master - slave if version is higher on slave, just not the other way around? normally no but take a look at the changelogs of myslq in the last years 80 out

RE: replication fails after upgrade to 5.6

It is safer to have the Slave be a newer version. -Original Message- From: Reindl Harald [mailto:h.rei...@thelounge.net] Sent: Thursday, February 21, 2013 10:30 AM To: mysql@lists.mysql.com Subject: Re: replication fails after upgrade to 5.6 Am 21.02.2013 19:11, schrieb Mike

Re: replication fails after upgrade to 5.6

@lists.mysql.com Subject: Re: replication fails after upgrade to 5.6 Am 21.02.2013 19:11, schrieb Mike Franon: Is the only way to really fix this is to upgrade master? I thought you can replicate from master - slave if version is higher on slave, just not the other way around? normally no but take

Re: replication fails after upgrade to 5.6

'data' for key 'PRIMARY'' on query. Default database: 'test'. Query: 'UPDATE IGNORE , Error_code: 1062 All of our other slaves on 5.0.96 are fine, so I know it has to do with 5.6 but just not sure what, when ir an mysql_upgrade everything was OK did you surely upgrade and restart the slaves

Re: replication fails after upgrade to 5.6

on 5.0.96 are fine, so I know it has to do with 5.6 but just not sure what, when ir an mysql_upgrade everything was OK did you surely upgrade and restart the slaves first? i personally would NOT go to 5.6 now it is a very young release and looking and the typical changelogs replication has

replication fails after upgrade to 5.6

So I successfully upgraded a test db server from 5.0.96 all the way up to 5.6 Replication as the slave, where the master is 5.0.96, started working for about 10 minutes and then got the following error: [ERROR] Slave SQL: Error 'Duplicate entry 'data' for key 'PRIMARY'' on query. Default

problems with mysql and php after system software upgrade

During a recent system software upgrade (CentOS) on the front-end of our computing cluster, the mysql area was upgraded without our realizing that it was going to be. Now, php and mysql do not communicate well with one another. The version of mysql on the system after the upgrade is 5.1.61

RE: mysql 5.5.24/27 massive slow down since upgrade to solaris 10 u9 with 147440-19

upgrade to solaris 10 u9 with 147440-19 Hello For nearly 3 years, we have had a master - slaves configuration working like a charm, the slaves would be able to sync daily ... since a recent upgrade from Solaris10u6 to solaris 10 u9 with the latest CPU bundle (kernel patch 147440-19) on one

mysql 5.5.24/27 massive slow down since upgrade to solaris 10 u9 with 147440-19

Hello For nearly 3 years, we have had a master - slaves configuration working like a charm, the slaves would be able to sync daily ... since a recent upgrade from Solaris10u6 to solaris 10 u9 with the latest CPU bundle (kernel patch 147440-19) on one of the two slaves, the slave upgrade cannot

Re: Upgrade 5.0 - 5.1 - long table names with invalid chars.

On 2/15/2012 22:16, Bobb Crosbie wrote: Hi Folks, I'm preparing an upgrade of a 5.0.51a database to 5.1.58 (Ubuntu 11.10) - Some of the table names contain invalid characters which mysql_upgrade (mysqlcheck) is attempting to escape by renaming the filename. However I'm having trouble with some

Upgrade 5.0 - 5.1 - long table names with invalid chars.

Hi Folks, I'm preparing an upgrade of a 5.0.51a database to 5.1.58 (Ubuntu 11.10) - Some of the table names contain invalid characters which mysql_upgrade (mysqlcheck) is attempting to escape by renaming the filename. However I'm having trouble with some tables with long names. For instance

puzzled issue for deadlock due to locking upgrade from LOCK_S to LOCK_X

are the same. uk_daily_sum_userid is the index that contains user_id and ratedate. Seen from the innodb provided information, we could deduce that: T1 Waiting for a LOCK_X for Record R1 T2 Hods a LOCK_S of Record R1, and waiting for a LOCK_X for R1 As T2 needs a lock upgrade but that is a LOCK_X

How often should we upgrade MySQL version

We are running MySQL 5.1.46 with master to master replication with 3 other servers for 3 different websites in 3 different parts of the world. My question is how often should we be looking to upgrade our MySQL version considering we can't really afford any downtime. Thanks Neil -- MySQL

RE: How often should we upgrade MySQL version

Ever heard the old saying, If it ain't broke, don't fix it. ;-) I'd say that as a general rule: 1. if you aren't experiencing problems then don't upgrade. 2. if you aren't subject to any vulnerabilities that may be found, then don't upgrade 3. if you don't need a new feature introduced

Re: How often should we upgrade MySQL version

I love the answer On Fri, Nov 18, 2011 at 10:59 PM, Daevid Vincent dae...@daevid.com wrote: Ever heard the old saying, If it ain't broke, don't fix it. ;-) I'd say that as a general rule: 1. if you aren't experiencing problems then don't upgrade. 2. if you aren't subject to any

strange warnings after upgrade...

We just upgraded our mysql from 5.0.32 on debian lenny, to 5.1.49 on debian squish. I wasn't told that it was doing an incremental version upgrade, i was under the impression it was just going from 5.0.32 to 5.0.8x. Anyways, I am getting some weird issues now, that is filling up the syslog

Re: strange warnings after upgrade...

To: mysql@lists.mysql.com Sent: Thursday, 4 August, 2011 4:17:50 PM Subject: strange warnings after upgrade... We just upgraded our mysql from 5.0.32 on debian lenny, to 5.1.49 on debian squish. I wasn't told that it was doing an incremental version upgrade, i was under the impression

Re: MySQL upgrade from 5.0.51a to 5.1.53

Hi all, I did a upgrade from 5.0 to 5.1 yesterday. And I paste some of my steps on the following. 1. Use mysqldump to dump all the data to the disk. 2. Backup all the data including mysql system files to a safe place. 3. Remove all the file related to mysql. 4. Install the new

MySQL upgrade from 5.0.51a to 5.1.53

HI Guys I found some info regarding a method to upgrade mysql databases. Currently the version is at mysql-5.0.51a (as installed via the ubuntu-8.0.4 respository). I downloaded the only version available from the web (5.1.53) that will work on ubuntu [except

Re: MySQL upgrade from 5.0.51a to 5.1.53

I suspect you need to have the new version running instead of the old one, for the mysql_upgrade script to work. On Tue, Nov 30, 2010 at 11:23 AM, Machiel Richards machi...@rdc.co.zawrote: HI Guys I found some info regarding a method to upgrade mysql databases. Currently

Re: MySQL upgrade from 5.0.51a to 5.1.53

vegiv...@tuxera.be To: Machiel Richards machi...@rdc.co.za Cc: mysql mailing list mysql@lists.mysql.com Subject: Re: MySQL upgrade from 5.0.51a to 5.1.53 Date: Tue, 30 Nov 2010 11:29:29 +0100 I suspect you need to have the new version running instead of the old one, for the mysql_upgrade script

RESOLVED - Re: MySQL upgrade from 5.0.51a to 5.1.53

HI All Just to let you know (if someone should be wondering) I used the method below on a VM in order to test the methods of upgrading before I do the actual systems. I was able to do a successful upgrade with no errors as far as I can see, using the method as described

Re: upgrade from version 5.0.45

On Sun, Apr 4, 2010 at 9:29 PM, Walter Heck - OlinData.com li...@olindata.com wrote: Depending on the seriousness of your environment you can read the changelogs and upgrade if you don't see any showstoppers. I have hardly ever seen any problems with minor version upgrades of mysql. Of course

Re: upgrade from version 5.0.45

On Tue, Mar 30, 2010 at 6:36 AM, Marco Baiguera marco.baigu...@gmail.com wrote: Hello everyone, i am quite new to mysql and i recently begin to work with a company who is using mysql 5.0.45 in production. i think this version is too old and would like to upgrade to the most recent 5.0.xx my

Re: upgrade from version 5.0.45

Depending on the seriousness of your environment you can read the changelogs and upgrade if you don't see any showstoppers. I have hardly ever seen any problems with minor version upgrades of mysql. Of course what Rob says is true, and it is a good idea to test things out in a test environment

Re: upgrade from version 5.0.45

might still have that bug. Jesper On 05/04/2010, at 2:29 PM, Walter Heck - OlinData.com wrote: Depending on the seriousness of your environment you can read the changelogs and upgrade if you don't see any showstoppers. I have hardly ever seen any problems with minor version upgrades of mysql

RE: upgrade from version 5.0.45

Hey if you are using any archive engines in your existing database then please use (5.0.8x) if not then u can upgrade to 5.1.45 (stable). Thanks, Dilipkumar -Original Message- From: ing.baigu...@gmail.com [mailto:ing.baigu...@gmail.com] On Behalf Of Marco Baiguera Sent: Tuesday, March 30

upgrade from version 5.0.45

Hello everyone, i am quite new to mysql and i recently begin to work with a company who is using mysql 5.0.45 in production. i think this version is too old and would like to upgrade to the most recent 5.0.xx my os is CentOS release 5.3. is it safe to simply use yum upgrade mysql

MySQL 5.1+ Upgrade on Solaris 10

Hello, Would appreciate if any you post the steps to upgrade MySQL 5.0 to higher versions (5.1, 5.4)on Solaris 10 ,X_64 box. Thanks Regards, S Paul

Mysql Upgrade from version 4 to 5

Hi Guys, Iam going to upgrade mysql version 4 to version 5.x on redhat ES4 . is there any particular way to do that ? if i take a mysqldump of the database and simply restore on to version 5 will work ? are there any differences between syntaxes/db structure etc on those 2 versions ? Thanks

RE: Mysql Upgrade from version 4 to 5

See: http://dev.mysql.com/doc/refman/5.0/en/upgrade.html -Original Message- From: Tharanga Abeyseela [mailto:tharanga.abeyse...@gmail.com] Sent: Wednesday, October 21, 2009 2:34 PM To: mysql@lists.mysql.com Subject: Mysql Upgrade from version 4 to 5 Hi Guys, Iam going to upgrade mysql

Re: upgrade 5.0.51 to 5.1.36 - TRUNCATE/DROP on temp table?

Per Jessen wrote: mysql list, after my upgrade to 5.1.36 I hit this odd little problem: I have an application which does roughly this: CREATE TEMP TABLE new LIKE old; populate 'new'. do some stuff TRUNCATE new; populate again This has always worked fine, but after the upgrade

upgrade from 5.0.51 to 5.1.36 - unexpected new databases?

mysql list, this weekend I upgraded my 5.0.51 installation to 5.1.36, which seems to have gone without a hitch - except the following weird messages: Failed to ALTER DATABASE `#mysql50#.protected` UPGRADE DATA DIRECTORY NAME Error: Table 'mysql.event' doesn't exist Failed to ALTER DATABASE

upgrade 5.0.51 to 5.1.36 - TRUNCATE/DROP on temp table?

mysql list, after my upgrade to 5.1.36 I hit this odd little problem: I have an application which does roughly this: CREATE TEMP TABLE new LIKE old; populate 'new'. do some stuff TRUNCATE new; populate again This has always worked fine, but after the upgrade it failed because the user does

storage upgrade in a replication cluster

All, I would appreciate some valuable ideas from you all. I have a replication setup with 1 master and 4 slaves, I am short on disk space on all the 5 servers so I will move to another partition (SAN). What is, according to you, the smoothest way to move all 5 servers from one partition to

storage upgrade in a replication cluster

All, I would appreciate some valuable ideas from you all. I have a replication setup with 1 master and 4 slaves, I am short on disk space on all the 5 servers so I will move to another partition (SAN). What is, according to you, the smoothest way to move all 5 servers from one partition to

Upgrade question

Hello MySQL users, My company is planning to upgrade from MySQL 5.0.51a to a more recent version. Which version of MySQL offers the best balance between stability and currency? Is there a discussion of the tradeoffs involved between different recent version that I could

Re: Upgrade Mysql

Thank You for all the help. I was upgrading from 4.0.x to 5.0.x The new mysql recognized the old databases without problems. Bye :)

Upgrade Mysql

Hi, I need to upgrade Mysql 4 to Mysql 5 on Linux. I will uninstall version 4 and install version 5. With uninstallation usually database files remain in /var/lib/mysql/ I want to know if with the installation of Mysql 5 those database will be recognized and imported

Re: Upgrade Mysql

On May 20, 2009, at 1:27 AM, Webmaster Studio Informatica wrote: I need to upgrade Mysql 4 to Mysql 5 on Linux. Sometimes I will uninstall version 4 and install version 5. With uninstallation usually database files remain in /var/lib/mysql/ I want to know if with the installation

Re: Upgrade Mysql

On Wed, May 20, 2009 at 10:27:51AM +0200, Webmaster Studio Informatica wrote: Hi, I need to upgrade Mysql 4 to Mysql 5 on Linux. I will uninstall version 4 and install version 5. With uninstallation usually database files remain in /var/lib/mysql/ I

Re: Upgrade Mysql

, then start it. Then you'll need to run mysqlupgrade. Depending on the size of your database and type of tables you are using it can take a while. For InnoDB tables, for example, upgrade simply means copy to tmp table... that's really slow if you have a large table. Once mysqlupgrade runs

Re: Upgrade Mysql

tables, for example, upgrade simply means copy to tmp table... that's really slow if you have a large table. Once mysqlupgrade runs without a hitch, you should be back in business. -Paul Webmaster Studio Informatica wrote: Hi, I need to upgrade Mysql 4 to Mysql 5 on Linux. I

Mysql upgrade from 4.1 to 5.0 to 5.1

Hi All, I've performed a upgrade from 4.1.22 to 5.0.81, the mysql_upgrade performed well on all tables repairing, however, after upgrade the same db from 5.0.81 to 5.1.33, a few tables got the error as below: Error: Unknown table engine 'InnoDB' error: Corrupt Any ideas? THnaks

Re: Mysql upgrade from 4.1 to 5.0 to 5.1

kengheng wrote: Hi All, I've performed a upgrade from 4.1.22 to 5.0.81, the mysql_upgrade performed well on all tables repairing, however, after upgrade the same db from 5.0.81 to 5.1.33, a few tables got the error as below: Error: Unknown table engine 'InnoDB' error: Corrupt Any

Re: Mysql upgrade from 4.1 to 5.0 to 5.1

A DB politics between mysql oracle again Thats quite ironic given recent events :) -- Linux web infrastructure consulting, cr...@codenation.net Free live poker tournament listings, http://www.g5poker.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql

Upgrade large databases from 4.1 to 5.1

Hi All, I need to migrate a large (30G) database from 4.1 to 5.1 on a live system that cannot afford a large amount of downtime. The official method (copy files, run mysql_upgrade...etc) is looking like it will take forever, particularly since I need to move it 5.0 before 5.1. How do

Re: Upgrade large databases from 4.1 to 5.1

If you can't take downtime, I'd go the slave route. You should certainly test your application to make sure 5.1's differences (data types, syntax, etc) don't cause problems. Otherwise you're risking getting badly stuck and having to downgrade to 4.1 again in a crisis. If you dump and reload,

Re: Upgrade large databases from 4.1 to 5.1

Baron Schwartz wrote: If you can't take downtime, I'd go the slave route. You should certainly test your application to make sure 5.1's differences (data types, syntax, etc) don't cause problems. Otherwise you're risking getting badly stuck and having to downgrade to 4.1 again in a crisis. If

Re: Upgrade large databases from 4.1 to 5.1

Craig, It is both feasible and dangerous. Good to hear you plan to put it through a couple of QA cycles (you will need them), but this can be accomplished. With a planned downtime window of an hour, I migrated a couple of terabytes from 4.0 to 5.0 a couple years back while making numerous schema

RE: Upgrade story / request for insight

-Original Message- From: walterh...@gmail.com [mailto:walterh...@gmail.com] On Behalf Of Walter Heck Sent: Wednesday, February 25, 2009 11:43 PM To: Jerry Schwartz Cc: Gary W. Smith; Claudio Nanni; MySql Subject: Re: Upgrade story / request for insight Maybe this could help you: http

Re: Upgrade story / request for insight

an upgrade which involves filesystem and services installation is quite different between Win and Linux. From a 'service' point of view (MySQL server) there will be no difference for any client in accessing a Win or a Linux box, but from a maintenance point of view you are facing problems

RE: Upgrade story / request for insight

. This means that you are probably running an older version of CentOS as 5.x comes with mysql 5.0 (I believe). You might want to setup a similar environment with the same OS and do a db upgrade on that (without your actual data) and see if everything works first. You might find some lib issues

RE: Upgrade story / request for insight

From: Claudio Nanni [mailto:claudio.na...@gmail.com] Sent: Wednesday, February 25, 2009 3:51 PM To: Jerry Schwartz Cc: MySql Subject: Re: Upgrade story / request for insight Hi Jerry, probably does not help you very much and excuse me in advance for this, [JS] No apology necessary

RE: Upgrade story / request for insight

From: Gary W. Smith [mailto:g...@primeexalia.com] Sent: Wednesday, February 25, 2009 4:36 PM To: Claudio Nanni; Jerry Schwartz Cc: MySql Subject: RE: Upgrade story / request for insight Jerry, To touch a little more on Claudio's statement, you are trying to compare monkey's and trucks

Re: Upgrade story / request for insight

Subject: RE: Upgrade story / request for insight Jerry, To touch a little more on Claudio's statement, you are trying to compare monkey's and trucks when you talk about mysql on these two different OS's. Microsoft is a different best when it comes to the install. [JS] That part I understand

Upgrade story / request for insight

My ultimate goal is to upgrade a production server (MySQL 4.1.22 on CentOS) to a modern 5.1 release. My development system is a Windows Vista x86 machine, and although the process is not that similar I decided to try an upgrade there. (I've never done one.) I figured this would give me some

what is best upgrade plan for large, replicating database?

, and reloading the database, would take too long. Also the databases are replicating. I believe I need to upgrade the slaves first, the go to the master. I've read about the possibility of having to rebuild indexes, mainly due to collation changes. I didn't see any compatibility issues in going

Re: what is best upgrade plan for large, replicating database?

?) The db is about 4 terabytes. This means making a dump of the database, installing a new version of the dbms, and reloading the database, would take too long. Also the databases are replicating. I believe I need to upgrade the slaves first, the go to the master. I've read about

Re: Upgrade from 4.0.26 to 5.0.67

to another, you should go to the next series rather than skipping a series. If you wish to upgrade from a release series previous to MySQL 4.1, you should upgrade to each successive release series in turn until you have reached MySQL 4.1, and then proceed with the upgrade to MySQL 5.0. For example

Unable to upgrade to 5.0: Address already in use

I have a strange problem: we have two OpenBSD 4.3 AMD64 servers. We upgraded one of them from 4.1 to 5.0 with no problem. But we are unable to upgrade the second one! All the compilation and installation is OK (version 5.0.67). But when we try to run the server it stops and the following

Upgrade from 4.0.26 to 5.0.67

Hi! I wish to upgrade the MySQL on a web server (Novell 6.5 sp6 - Apache 2, MySQL ver. 4.0.26, PHP 5.2.3) to 4.1.2 or 5.0.67. Is there any possibility to upgrade directly from MySQL 4.0.26 to 5.0.67, without upgrading first to the intermediate versions? TIA Nanu -- MySQL General Mailing

Re: Upgrade from 4.0.26 to 5.0.67

Nanu Kalmanovitz schrieb: Hi! I wish to upgrade the MySQL on a web server (Novell 6.5 sp6 - Apache 2, MySQL ver. 4.0.26, PHP 5.2.3) to 4.1.2 or 5.0.67. Is there any possibility to upgrade directly from MySQL 4.0.26 to 5.0.67, without upgrading first to the intermediate versions? yes

Re: Upgrade from 4.0.26 to 5.0.67

FYI the manual for 5.0 recommends upgrading to 4.1 first. As a general rule, we recommend that when upgrading from one release series to another, you should go to the next series rather than skipping a series. If you wish to upgrade from a release series previous to MySQL 4.1, you should

Mysql Upgrade to 3.23.58 issue in Fedora Core 2

Hello I ram yum update for mysql , mysql-server and mysql-devel in fedora core 2, after this mysql is not starting. === Log Error message: 080715 22:55:58 mysqld started Cannot initialize InnoDB as 'innodb_data_file_path' is not set. If you do not want to use transactional InnoDB

information_schema errors after (minor) upgrade

Running a FreeBSD system and mysql 5.0.27 server, I recently upgraded to 5.0.51 (but kept the 5.0.27 client). Everything seemed fine, until I ran a databse check today: Checking information_schema:CHARACTER_SETS Checking information_schema:COLLATIONS Checking

RE: information_schema errors after (minor) upgrade

: information_schema errors after (minor) upgrade Running a FreeBSD system and mysql 5.0.27 server, I recently upgraded to 5.0.51 (but kept the 5.0.27 client). Everything seemed fine, until I ran a databse check today: Checking information_schema:CHARACTER_SETS Checking information_schema:COLLATIONS Checking

Replication Issue with Upgrade from 4.0.x to 5.0.x

I'm trying to upgrade the master to, also. After synchronizing the databases, I've run 'reset master' and 'reset slave' on their respective servers, then 'change master to...' on the slave, but 'show slave status' always displays: 'Slave_IO_Running: No' And here is the log entry from the slave

Re: Replication Issue with Upgrade from 4.0.x to 5.0.x

is running on CentOS 5, which is what I'm trying to upgrade the master to, also. After synchronizing the databases, I've run 'reset master' and 'reset slave' on their respective servers, then 'change master to...' on the slave, but 'show slave status' always displays: 'Slave_IO_Running: No' And here

Re: Replication Issue with Upgrade from 4.0.x to 5.0.x

on CentOS 5, which is what I'm trying to upgrade the master to, also. After synchronizing the databases, I've run 'reset master' and 'reset slave' on their respective servers, then 'change master to...' on the slave, but 'show slave status' always displays: 'Slave_IO_Running: No' And here

Re: Replication Issue with Upgrade from 4.0.x to 5.0.x

and the slave is running on CentOS 5, which is what I'm trying to upgrade the master to, also. After synchronizing the databases, I've run 'reset master' and 'reset slave' on their respective servers, then 'change master to...' on the slave, but 'show slave status' always displays

Re: Replication Issue with Upgrade from 4.0.x to 5.0.x

Dave: There are no uncommented entries in /etc/hosts.deny Baron: The all servers have a unique server-id in their respective my.cnf's When I try to connect directly from the slave to the new master, I get: ERROR 2003 (HY000): Can't connect to MySQL server on '1xx.1xx.1xx.xx' (113)

  1   2   3   4   5   6   7   >