Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Upgrade from Mysql Community to Enterprise

1,393 views
Skip to first unread message

Iass

unread,
Dec 4, 2008, 1:23:06 PM12/4/08
to
Hi,

We are going to upgrade from Mysql Community version 5.0.45 to Mysql
Enterprise 5.0.68. I've been looking around for directions on how to make
this move as flawless and speedy as possible but the information is not
abundant IMHO. Our database has a ibdata1 file of 60 Gbyte so dumping and
loading afterwards is would require to much time (approx 3 hours to dump
and 7 to load again).
I would appreciate any suggestion.

regards,

Ivan

Axel Schwenke

unread,
Dec 4, 2008, 2:58:24 PM12/4/08
to
Iass <ia...@gmeel.kom> wrote:
>
> We are going to upgrade from Mysql Community version 5.0.45 to Mysql
> Enterprise 5.0.68. I've been looking around for directions on how to make
> this move as flawless and speedy as possible but the information is not
> abundant IMHO. Our database has a ibdata1 file of 60 Gbyte so dumping and
> loading afterwards is would require to much time (approx 3 hours to dump
> and 7 to load again).

There is no difference between Community and Enterprise in that
respect. Instructions for upgrading Community->Community and also
Enterprise->Enterprise will work for you.


XL

saezsc...@gmail.com

unread,
Dec 5, 2008, 4:23:07 AM12/5/08
to
On Dec 4, 8:58 pm, Axel Schwenke <axel.schwe...@gmx.de> wrote:

Xl,

But what are the instruction for upgrading from, lets say, community
5.0.45 to community 5.0.68 on a Red Hat environment?
I'm planning to do the following:
1) make a backup (everything: software, /etc/my.cnf, datadir files)
2) remove Mysql 5.0.45 (rpm -e)
3) install 5.0.68 (rpm -i)
4) restore /etc/my.cnf from backup
5) start mysql

At this Mysql 5.0.68 should be using the datafile from 5.0.45. is this
a correct action plan?
I've reading http://dev.mysql.com/doc/refman/5.0/en/upgrade.html but
it is not very specific (for my case).

regards,

Ivan

Axel Schwenke

unread,
Dec 5, 2008, 6:28:56 AM12/5/08
to
saezsc...@gmail.com wrote:

> On Dec 4, 8:58=A0pm, Axel Schwenke <axel.schwe...@gmx.de> wrote:
>>
>> There is no difference between Community and Enterprise in that
>> respect. Instructions for upgrading Community->Community and also
>> Enterprise->Enterprise will work for you.
>
> But what are the instruction for upgrading from, lets say, community
> 5.0.45 to community 5.0.68 on a Red Hat environment?
> I'm planning to do the following:
> 1) make a backup (everything: software, /etc/my.cnf, datadir files)
> 2) remove Mysql 5.0.45 (rpm -e)
> 3) install 5.0.68 (rpm -i)
> 4) restore /etc/my.cnf from backup
> 5) start mysql

I rather suggest:

1) make a backup of my.cnf and dump your data; alternatively you can
copy the datadir, but this requires a downtime of the server.
Copying the datadir while the MySQL server is running will *not*
yield a proper backup but garbage.
This step is optional and purely for safety of your data. And of
course you do make regular backups anyway, don't you? ;)

2) get the new packages and run rpm -U <list of new packages>
rpm will handle all this:
- stop the running server
- remove old packages
- install new packages
- start new server

For the "remove old" step you have to upgrade *all* installed
MySQL RPMs. I.e. if you have mysql-server, mysql-client and
mysql-shared from 5.0.45, you must upgrade all of those.

When you upgrade from Community to Enterprise, this might be a
problem if the packages are differently split. In that case do
it manually:

- stop MySQL
- uninstall old rpms (will not remove data/config)
- install new rpms (will not overwrite data/config, will start
the server)

3) check if your old my.cnf is still in place (it should) and
if the MySQL server is up and running (it should)

4) run mysql_upgrade; this is probably a NULL operation for 5.0.45
to 5.0.68 but you should always do it.


XL

manish...@appcino.com

unread,
Dec 7, 2016, 3:41:36 AM12/7/16
to
--
*The information in this email, including all attachments, is confidential
and for use by the addressee(s) only. If you are not the intended
recipient, please return the email to the sender and delete it from your
computer.*
0 new messages