Am 20.02.2013 18:26, schrieb Mike Franon:
So I did a full mysqldump over the weekend for a second time and this
time it is 220GB, no clue what happened last time, I should have
realized looking at the file size something was wrong, but since I got
no errors did not think about it, and this
So I did a full mysqldump over the weekend for a second time and this
time it is 220GB, no clue what happened last time, I should have
realized looking at the file size something was wrong, but since I got
no errors did not think about it, and this time I timed it, took 7
hours to do a complete
I am pretty sure I did, and when I did I got the following errors:
Error: Table Upgrade Required, Please dump/reload to fix it
I got that on 10 tables, and also got the following:
Warning: Triggers for table ' have no creation context.
I think it has to do with no triggers.
I know hen I
OK I got it to work.
I dumped the tables that it was complaining about first, and then
dumped the triggers.
I then uninstalled anything to do with mysql, and installed 5.1
Then imported the tables and triggers, and and able to run
mysql_upgrade without any errors.
This is all without using a
fine and much faster and probably safer too :-)
a backup with rsync is faster as dump/import and
can be done with minimize downtime by use it
twice, the first time hot-backup with running
server and the second time after stop server
to get the diffs
doing rsync - stop - rsync - start in a script
going form 5.1 - to 5.5 was easy, I did not have to dump any tabels or
triggers, just upgraded binary, ran mysql_upgrade and worked in no
time.
Thanks everyone for the help!
On Wed, Feb 20, 2013 at 2:33 PM, Reindl Harald h.rei...@thelounge.net wrote:
fine and much faster and probably safer too
surely
* use mysql_upgrade -u root -p after EACH update
* upgrade regulary
we went from MySQL 3.x to 5.5.30 until know without
any dump and here are around 5000 tables
Am 19.02.2013 22:12, schrieb Divesh Kamra:
Is there any better way for grade MySQL version without taking backup with
Use replication as your fail over and why not percona's xtrabackup or lvm type
backup if you need a backup?
Sabika
On Feb 19, 2013, at 1:20 PM, Reindl Harald h.rei...@thelounge.net wrote:
surely
* use mysql_upgrade -u root -p after EACH update
* upgrade regulary
we went from MySQL
Hi Reindi
Thanks for solution .
Can u share complete steps ?
R's
DK
On 20-Feb-2013, at 2:50, Reindl Harald h.rei...@thelounge.net wrote:
surely
* use mysql_upgrade -u root -p after EACH update
* upgrade regulary
we went from MySQL 3.x to 5.5.30 until know without
any dump
Am 19.02.2013 23:53, schrieb Divesh Kamra:
Hi Reindi
Thanks for solution .
Can u share complete steps ?
which steps?
* update
* call mysql_upgrade -u root -p
in doubt mysqlcheck -h localhost --check-upgrade --all-databases --auto-repair
--user=root -p
and if you do
Hi all
Is there any better way for grade MySQL version without taking backup with
mysqldump
Or if there any tool for this
R's
DK
On 16-Feb-2013, at 16:07, Reindl Harald h.rei...@thelounge.net wrote:
Am 16.02.2013 09:42, schrieb Manuel Arostegui:
2013/2/15 Reindl Harald
2013/2/15 Reindl Harald h.rei...@thelounge.net
our database is 400 GB, mysqldump is 600MB was not a typo and you
honestly believed that you can import this dump to somewhat?
WTF - as admin you should be able to see if the things in front
of you are theoretically possible before your start
Am 16.02.2013 09:42, schrieb Manuel Arostegui:
2013/2/15 Reindl Harald h.rei...@thelounge.net
mailto:h.rei...@thelounge.net
our database is 400 GB, mysqldump is 600MB was not a typo and you
honestly believed that you can import this dump to somewhat?
WTF - as admin you
PM
To: Rick James
Cc: Mihail Manolov; Mike Franon; Akshay Suryavanshi; mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
Its a very pedantic case, but we had a few instances where it was an issue
at my last job. It basically involved multi-table deletes
with precedence of commajoin vs
explicit
JOIN.
From: Singer Wang [mailto:w...@singerwang.com]
Sent: Thursday, February 14, 2013 3:41 PM
To: Rick James
Cc: Mihail Manolov; Mike Franon; Akshay Suryavanshi;
mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
: Mihail Manolov; Mike Franon; Akshay Suryavanshi;
mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
Its a very pedantic case, but we had a few instances where it was an
issue
at my last job. It basically involved multi-table deletes and aliasing..
I
Am 15.02.2013 22:55, schrieb Mike Franon:
I am having a real hard time upgrading just from 5.0.96 to 5.1
I did a full mysqldump and then restore the database, keep in mind our
database is 400 GB, mysqldump is 600MB file, about 30 minutes into the
restore get this error on one table on an
vs
explicit
JOIN.
From: Singer Wang [mailto:w...@singerwang.com]
Sent: Thursday, February 14, 2013 3:41 PM
To: Rick James
Cc: Mihail Manolov; Mike Franon; Akshay Suryavanshi;
mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
: Thursday, February 14, 2013 3:41 PM
To: Rick James
Cc: Mihail Manolov; Mike Franon; Akshay Suryavanshi;
mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
Its a very pedantic case, but we had a few instances where it was an
issue
at my
of commajoin vs
explicit
JOIN.
From: Singer Wang [mailto:w...@singerwang.com]
Sent: Thursday, February 14, 2013 3:41 PM
To: Rick James
Cc: Mihail Manolov; Mike Franon; Akshay Suryavanshi;
mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
Its a very pedantic case
@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
Its a very pedantic case, but we had a few instances where it was an
issue
at my last job. It basically involved multi-table deletes and
aliasing..
I
quote the change notes for MySQL 5.5.3
Incompatible
...@singerwang.com]
Sent: Thursday, February 14, 2013 3:41 PM
To: Rick James
Cc: Mihail Manolov; Mike Franon; Akshay Suryavanshi;
mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
Its a very pedantic case, but we had a few instances where it was an
issue
at my last job
.
From: Singer Wang [mailto:w...@singerwang.com]
Sent: Thursday, February 14, 2013 3:41 PM
To: Rick James
Cc: Mihail Manolov; Mike Franon; Akshay Suryavanshi;
mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
Its a very pedantic case, but we had a few
To: Rick James
Cc: Mihail Manolov; Mike Franon; Akshay Suryavanshi;
mysql@lists.mysql.com mailto:mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
Its a very pedantic case, but we had a few instances where
2013/2/14 Mike Franon kongfra...@gmail.com
Great thanks for the info, I guess the best way to do this is take a
spare server, set it up with our standard setup, and then start the
upgrade as you said 5.0 - 5.1 - 5.5, test and then upgrade to 5.6
and test.
Do not forget to leave that spare
Great thanks for the info, I guess the best way to do this is take a
spare server, set it up with our standard setup, and then start the
upgrade as you said 5.0 - 5.1 - 5.5, test and then upgrade to 5.6
and test.
On Thu, Feb 14, 2013 at 4:22 PM, Akshay Suryavanshi
Mike,
5.6 is GA now, so its stable release. Also you should not jump to 5.6
directly, atleast from 5.0.
There are many bug fixes and changes in 5.1, so you should consider this
way.
5.0--5.1--5.5 (all slaves first, and then the master)
And further 5.5 -- 5.6 (again all slaves first and then
the way to 5.6? Maybe. You need to do a lot of shakedown
anyway.
-Original Message-
From: Mihail Manolov [mailto:mihail.mano...@liquidation.com]
Sent: Thursday, February 14, 2013 2:22 PM
To: Mike Franon
Cc: Akshay Suryavanshi; mysql@lists.mysql.com
Subject: Re: Upgrading form mysql
Singer, do you have some examples?
-Original Message-
From: Singer Wang [mailto:w...@singerwang.com]
Sent: Thursday, February 14, 2013 2:59 PM
To: Mihail Manolov
Cc: Mike Franon; Akshay Suryavanshi; mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
...@liquidation.com]
Sent: Thursday, February 14, 2013 3:30 PM
To: Rick James
Cc: Singer Wang; Mike Franon; Akshay Suryavanshi;
mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
The ones that didn't work for me required table rearrangement in the
query. MySQL 5.5 was very
, the other with precedence of commajoin vs explicit
JOIN.
From: Singer Wang [mailto:w...@singerwang.com]
Sent: Thursday, February 14, 2013 3:41 PM
To: Rick James
Cc: Mihail Manolov; Mike Franon; Akshay Suryavanshi; mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
Its a very
To: Mihail Manolov
Cc: Mike Franon; Akshay Suryavanshi; mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
There are queries that works with 5.1/5.0 that do not work with 5.5, I
would test extensively..
S
On Thu, Feb 14, 2013 at 5:22 PM, Mihail Manolov
You could jump from 5.0 directly to 5.5 and skip 5.1. I have without any
issues. There are some configuration file change, which you may want to
consider checking. I definitely recommend upgrading your development servers
for an extensive testing. Some queries _may_ run slower or not work at
There are queries that works with 5.1/5.0 that do not work with 5.5, I
would test extensively..
S
On Thu, Feb 14, 2013 at 5:22 PM, Mihail Manolov
mihail.mano...@liquidation.com wrote:
You could jump from 5.0 directly to 5.5 and skip 5.1. I have without any
issues. There are some
]
Sent: Thursday, February 14, 2013 2:59 PM
To: Mihail Manolov
Cc: Mike Franon; Akshay Suryavanshi; mysql@lists.mysql.com
Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
There are queries that works with 5.1/5.0 that do not work with 5.5, I
would test extensively..
S
On Thu, Feb
35 matches
Mail list logo
