Reindl,
I am sorry, in my original post, I forgot to mention that the OLD box and
the NEW box are the same physical machine. I need to be able to save all
data into files on a memstick or portable disc and restore them to the newly
staged machine (with the new version of mysql).
-Grant
--
Hi Grant,
On 12/26/2014 11:18 AM, Grant Peel wrote:
Reindl,
I am sorry, in my original post, I forgot to mention that the OLD box and
the NEW box are the same physical machine. I need to be able to save all
data into files on a memstick or portable disc and restore them to the newly
staged
Shawn all,
Thank you for taking to time to reply.
So, to be clear, what I understand from your post is that replacing the
new build's grant/system tables with the archived ones from the previous
version, generally works fine, upgrade issues not withstanding. This is the
answer I
Am 26.12.2014 um 20:52 schrieb Grant Peel:
Shawn all,
Thank you for taking to time to reply.
So, to be clear, what I understand from your post is that replacing the
new build's grant/system tables with the archived ones from the previous
version, generally works fine, upgrade issues not
Am 25.12.2014 um 16:01 schrieb Grant Peel:
I was wondering if anyone knows of a concise tutorial on how to upgrade (by
moving from one box (old) to another box (new) mysql in a virtual
environment (many mysql users, many databases).
Mysql 5.x setup on freebsd 8.x (x86/32b), call this box A.
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
That would work, yes.
You could also try to upgrade in place - the upgrade scripts *should* take
care of everything between those versions, I think. Make sure you have a
backup in any case :-)
On Mon, Nov 22, 2010 at 12:57 PM, Machiel Richards machi...@rdc.co.zawrote:
Hi All
Sorry
...@lists.mysql.com%3e
*Subject*: Re: Upgrading of mysql database
*Date*: Mon, 22 Nov 2010 15:25:44 +0100
That would work, yes.
You could also try to upgrade in place - the upgrade scripts *should* take
care of everything between those versions, I think. Make sure you have a
backup in any case
How would I do an inplace upgrade?
-Original Message-
From: Johan De Meersman vegiv...@tuxera.be
To: Machiel Richards machi...@rdc.co.za
Cc: mysql mailing list mysql@lists.mysql.com
Subject: Re: Upgrading of mysql database
Date: Mon, 22 Nov 2010 15:25:44 +0100
That would work, yes.
You
The issue is that in theory this should work given the facts announced
by MySQL regarding binary logging and replication.
I can certainly do it the way you propose, but to my mind I should also
be able to do it using the fact that both machines are fully synced and
hence at
that point I should
On 1/13/10 2:28 PM, Lawrence Sorrillo sorri...@jlab.org wrote:
The issue is that in theory this should work given the facts announced
by MySQL regarding binary logging and replication.
I can certainly do it the way you propose, but to my mind I should also
be able to do it using the fact that
On Jan 13, 2010, at 1:28 PM, Lawrence Sorrillo wrote:
The issue is that in theory this should work given the facts announced by
MySQL regarding binary logging and replication.
I can certainly do it the way you propose, but to my mind I should also be
able to do it using the fact that both
How about:
1 shut down the slave, upgrade it, restart it, let it catch up.
2 shut down the master, upgrade it, restart it, let the slave catch up.
?
On 1/12/10 12:34 PM, Lawrence Sorrillo sorri...@jlab.org wrote:
Hi:
I want to upgrade a master and slave server from mysql 4.1 to mysql
Also see http://dev.mysql.con/doc/refman/5.0/en/mysql-upgrade.html.
And make sure you make a backup before you do anything :)
-Original Message-
From: Tom Worster [mailto:f...@thefsb.org]
Sent: Tuesday, January 12, 2010 10:47 AM
To: Lawrence Sorrillo; mysql@lists.mysql.com
Subject: Re
This is two upgrades done in sequence(the reload takes about three hours
per machine) . I can do what I am proposing in parallel.
Do you see it as problematic?
~Lawrence
Tom Worster wrote:
How about:
1 shut down the slave, upgrade it, restart it, let it catch up.
2 shut down the master,
Lawrence Sorrillo wrote:
Hi:
I want to upgrade a master and slave server from mysql 4.1 to mysql 5.1.
I want to so something like follows:
1. Stop all write access to the master server.
ok
2. Ensure that replication on the slave is caught up to the last change
on the master.
why? You
Hi:
I want to ensure that right after the reload that the same data is
present in both the master and the slave. They are in perfect sync. Then
I think its safe to consider starting binary logging and replication
etc. And after these are started, changes can start?
And in setting up
On Jan 12, 2010, at 12:36 PM, Lawrence Sorrillo wrote:
Hi:
I want to ensure that right after the reload that the same data is present in
both the master and the slave. They are in perfect sync. Then I think its
safe to consider starting binary logging and replication etc. And after these
Frankly, I didn't entirely understand what you were proposing. I got lost
around step 6.
Is the issue total time for the procedure or service downtime?
On 1/12/10 12:58 PM, Lawrence Sorrillo sorri...@jlab.org wrote:
This is two upgrades done in sequence(the reload takes about three hours
per
Hi,
The step 6 in simple terms is
Here we need to build two server ( both master and slave ). Instead of
building two server as it takes double the time of building in one server.
After building an server, make a copy of the first server files at OS level
and copy it to the server and start the
Hi!
I don't do DBA work, so my info may be incomplete:
monem mysql wrote:
Hello
I have to upgrade many mysql databases from mysql 4 and 4.1 to 5.4 with a
large size 2.7 TB
[[...]]
The official method takes too much time. But I've read that we can use '*dump
and reload'* to
Using mysqldump and loading directly into 5.4 *might* work, but you should
never do any of this on your production system without testing.
Get another box, start with 4.1 and do the upgrade on a test server -- even
test your queries as there a few incompatible changes between 4 and 5. One you
David Harrison wrote:
Hi all,
I've got a quite large database (23G) that is running on a 5.0.32
version of MySQL. I really want to upgrade out of 5.0.32 to the
latest version of 5.1 (or even 5.4) but a straight mysql_upgrade of
the database takes long enough that I'd have serious
On Fri, Aug 28, 2009 at 9:18 AM, Shawn Green shawn.gr...@sun.com wrote:
Hank wrote:
Hello All,
I'm in the process of upgrading my database from 4.1 to 5.0 on CentOS.
I've been testing the mysqlcheck --check-upgrade --auto-repair
command,
and on one of my MYISAM tables, it's taking
Hank wrote:
Hello All,
I'm in the process of upgrading my database from 4.1 to 5.0 on CentOS.
I've been testing the mysqlcheck --check-upgrade --auto-repair command,
and on one of my MYISAM tables, it's taking forever to upgrade the table.
It has about 114 million rows, and I'm guessing it
What I always did since 3.23 upwards is new installation and import.
My tecnique allows me to install as many mysql instances as I want,
I always use specific user, homedir, datadir, my.cnf, for each installation.
In this way I can have theoretically unlimited number of mysql instances on
one
Hi Mat,
How many databases have you got running on 4.0? You can certainly go
through the motions of downloading each interim release, however my best
advice would be (if time/disk space permits) to dump your databases to
plain SQL files (using mysqldump) obliterate your 4.0 install, install
I would strongly suggest logging all your 4.0 queries for at least 24
hours and then running them on your new 5.x server to avoid any
surprises such as incompatible queries for example.
Good luck!
Mihail
On Mar 9, 2009, at 1:42 PM, Matthew Stuart wrote:
Hi all, I am on... wait for it...
On Mon, March 9, 2009 12:51, Mihail Manolov wrote:
I would strongly suggest logging all your 4.0 queries for at least 24
hours and then running them on your new 5.x server to avoid any
surprises such as incompatible queries for example.
Good luck!
Mihail
Good idea. I would pay particular
You may want to try replication. Setup your replication server as
5.0. That server gives you a chance to play to get things right
without affecting the master server. You'll still need to do a dump to
get the slave up to speed. Once you get everything right, you can
switch over and the
Hi,
Take backup of the existing data before upgrading for safety. There is RHEL 4
specific rpm binary is existing in the downloading section. After installing
run the required tools comes with mysql.
Before upgrading with existing datas read the documentation carefully.
Hi !
perl pra schrieb:
[[...]]
Also please tell me where can i get mysql5.1 enterprise edition.
5.1 is currently labeled rc (current version is 5.1.22-rc), so there
is no enterprise edition yet.
When there will be one, it will be for paying customers, and they have
got (or will receive) the
Seth Seeger wrote:
Hello,
I'm having trouble copying a database from MySQL 4.1.22 to 5.1.19-
beta. Both are FreeBSD i386-based machines. I have run the following
commands:
mysqlcheck --check-upgrade --all-databases --auto-repair
mysql_fix_privilege_tables
Both executed with no problems.
On Jun 21, 2007, at 12:21 PM, Gerald L. Clark wrote:
Seth Seeger wrote:
Hello,
I'm having trouble copying a database from MySQL 4.1.22 to 5.1.19-
beta. Both are FreeBSD i386-based machines. I have run the
following commands:
mysqlcheck --check-upgrade --all-databases --auto-repair
Hi Seth -
I believe MySQL's official position is that you should always dump-and-load
the data when upgrading major or minor versions (4.0 to 4.1, 4.1 to 5.0,
etc.)
I've done it both ways (dump-load and just moving table files) and have
never had a problem with either, even when moving files
Regarding the format of TIMESTAMP columns, one of the user comments on
http://dev.mysql.com/doc/refman/4.1/en/timestamp-4-1.html
offers the solution below:
Posted by Kjell Arne Rekaa on April 14 2005 11:11pm
If you want the same view of a timestamp field in 4.1.x as it was in
in earlier mysql
On 8/2/06, bruce [EMAIL PROTECTED] wrote:
hi..
i have FC3, with 4.1.13, i also have FC4 with 4.1.20. however, i can't seem
to find 5.0.x RPMs for FC3/4. do i have to go ahead and build this from
source for the FC3/4 boxes that i have...
Linux x86 generic RPM at:
Dan, I haven't seen any other responses, so I'll chime in with my $.02.
I think you should have very few problems upgrading from 3.23.58 to
5.0.22. I think you will in fact be able to do pretty much what you
describe.
I've upgraded in both fashions in the past (re-importing mysqldump
On 6/25/06, Dan Trainor [EMAIL PROTECTED] wrote:
Good morning, all -
I've read for quite a while tonight, but still haven't been able to
figure out - can I upgrade directly from 3.23.58 to 5.0.22?
I've read that I'd have to do something like 3.23.58 4.0 4.1
5.0.22, but then also the
Yes Eric You are correct. Thankyou for your reply. It helped me.
Bala
You need root privileges.
Login as root or use sudo. E.g.
sudo rpm -Uvh MySQL-shared-compat-5.0.19-0.rhel4.i386.rpm
If you don't have root or sudo access, you can't perform this upgrade.
You could possibly use the --prefix and --relocate rpm install options
to install mysql into a directory
Gary Richardson wrote:
We moved directly from 4.0.20 to 5.0.16. Worked like a charm. I had a
script that went through and optimized all tables with keys on
text/varchar and char fields.
We're also slowly ALTERing innodb tables to get them into the new
compact format.
i tryed to update from
Hello.
Manual recommends to perform an upgrade step by step. So
I suggest you to move to 4.1 at first. When you said 'tablespace'
have you meant that you're using InnoDB tables? I'm not sure about
them, check the change logs to find out any incompatible changes. In
case of MyISAM,very often
We moved directly from 4.0.20 to 5.0.16. Worked like a charm. I had a
script that went through and optimized all tables with keys on
text/varchar and char fields.
We're also slowly ALTERing innodb tables to get them into the new
compact format.
On 12/28/05, Gleb Paharenko [EMAIL PROTECTED]
PaginaDeSpud [EMAIL PROTECTED] wrote on 12/27/2005 03:33:58
PM:
hi,
I've upgraded from mysql 4.1 to mysql 5 and some queries doesn't work.
It's
not explained on mysql changes incompatibilities...
for example:
snip
FROM yabbse_topics, yabbse_messages, yabbse_messages as m2 LEFT JOIN
I've upgraded from mysql 4.1 to mysql 5 and some queries
doesn't work. It's not explained on mysql changes
incompatibilities...
It is: see the first change item, marked 'incompatible change', at
http://dev.mysql.com/doc/refman/5.0/en/news-5-0-12.html. We can no
longer get away with
.
- Original Message -
From: Peter Brawley [EMAIL PROTECTED]
To: PaginaDeSpud [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com
Sent: Tuesday, December 27, 2005 10:29 PM
Subject: Re: upgrading to mysql 5
/I've upgraded from mysql 4.1 to mysql 5 and some queries
doesn't work. It's not explained on mysql
When mysql had trouble starting up what error messages did it give in
the .err file in the datadir?
-Eric
James Tu wrote:
I had to migrate from 4.0.11 to 4.1.12. I saved the data directory from the
older version. I also exported all the information using phpMyAdmin's export
tool. I have one
PROTECTED]
Sent: Tuesday, March 29, 2005 8:40 PM
To: mysql@lists.mysql.com
Subject: Re: upgrading mysql on RH fedora core 3
On Tue, 29 Mar 2005 19:28:56 -0800, bruce [EMAIL PROTECTED] wrote:
we're trying to install mysql/mysql-server (4.1.10a-1.i386) and are
running
into some serious problems. we
On Tue, 29 Mar 2005 19:28:56 -0800, bruce [EMAIL PROTECTED] wrote:
we're trying to install mysql/mysql-server (4.1.10a-1.i386) and are running
into some serious problems. we had mysql/server (3.23.52-3.i386) running,
but needed to go to the higher version...
I was about to attempt the same
bruce wrote:
hi...
we're trying to install mysql/mysql-server (4.1.10a-1.i386) and are running
into some serious problems. we had mysql/server (3.23.52-3.i386) running,
but needed to go to the higher version...
can someone tell us how/what we need to do to get this working correctly.
actually,
On Tuesday, March 29, 2005 21:29, bruce wrote:
hi...
we're trying to install mysql/mysql-server (4.1.10a-1.i386) and are
running into some serious problems. we had mysql/server
(3.23.52-3.i386) running, but needed to go to the higher version...
can someone tell us how/what we need to do
On Tue, 29 Mar 2005 20:39:54 -0800, Florin Andrei
[EMAIL PROTECTED] wrote:
On Tue, 29 Mar 2005 19:28:56 -0800, bruce [EMAIL PROTECTED] wrote:
we're trying to install mysql/mysql-server (4.1.10a-1.i386) and are running
into some serious problems. we had mysql/server (3.23.52-3.i386) running,
Hello.
Please, search in MySQL archives (at lists.mysql.com/mysql) about
successful solutions to your problem. You may use --focre --nodeps
flags for the rpm command.
[snip]
I want to upgrade mysql client 3.23. to mysql 4.1.10
But when I type rpm -Uvh mysql-client-4.1...rpm
It's
zzapper wrote:
None of your db apps will now run!
It's something to do with a new password algorithm
You are supposed to be able to fix this by specifying old passwords in your new my.ini
You are also advised to upgrade Perl,PHP, Drivers etc
This issue has been raised basically every day in
Hello.
Install MySQL-client-4.1.10-0.i386.rpm.
Troy Richard [EMAIL PROTECTED] wrote:
I have upgraded from mysql 3.23 to 4.1.10 everything seems to be working.
I'm trying to run the mysql_fix_privilege_tables script to update the
privileges and I'm getting the following error:
Hello.
Try --complete-insert command line option for mysqldump. See:
http://dev.mysql.com/doc/mysql/en/mysqldump.html
[EMAIL PROTECTED] wrote:
Hi,
I just tried to upgrade from mysql 3.23.57 (SPARC/Solaris) to 4.1.9
(i386/Linux) using mysqldump but when importing the dump on the
Modify the insert statement so that you name the column you're inserting
to.
INSERT INTO `db` (put the column names in here)
VALUES('localhost','dbxxx','','Y','Y','Y','Y','Y','Y','N','Y','Y','Y'),.
..
Kevin Cowley
RD
Tel: 0118 902 9099 (direct line)
Email: [EMAIL PROTECTED]
Web:
I'm using Fedora Core 3 and just did an upgrade from 4.1.7 to 4.1.9,
using Linux AMD64 rpms from the MySQL web site. It looks like everything
went well. For me, the hard part was backing up my databases with
mysqldump -- see my comments under the thread MySQL upgrading on this
list.
I shut
Hello.
Yes, if you have one of the last releases of MySQL, you can try to test
the fifth version. But some features will be unavailable. See:
http://dev.mysql.com/doc/mysql/en/Upgrading-from-4.1.html
Jonathan Villa [EMAIL PROTECTED] wrote:
I have an installation of 4.1 and 5 running
Joshua J. Kugler wrote:
Take a look at http://mysql.he.net/doc/mysql/en/Upgrade.html
Hmmm... Can 4.1 mirror a 3.2 server? That might be a good deal easier.
--
A. Clausen
[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
Hello.
perror 13
Error code 13: Permission denied
Check if you have necessary permissions on your data directory.
Aaron E. Diehl [EMAIL PROTECTED] wrote:
Hello All,
I'm having trouble upgrading 3.23. to 4.1. Since I don't want to break
production, I'm trying to start a test
The 'gotchas' are listed in the manul for 3.23 to 4.0 here:
http://dev.mysql.com/doc/mysql/en/Upgrading-from-3.23.html
and from 4.0 to 4.1 here:
http://dev.mysql.com/doc/mysql/en/Upgrading-from-4.0.html
On Tue, 07 Dec 2004 16:01:51 -0800, A. Clausen [EMAIL PROTECTED] wrote:
I've been running,
Take a look at http://mysql.he.net/doc/mysql/en/Upgrade.html
j- k-
On Tuesday 07 December 2004 15:01, A. Clausen said something like:
I've been running, with great success, version 3.23.58 on my Win2k box
for quite a while now, but am interested in moving up to 4.1. Is there
any
Stembridge, Michael wrote:
I have tried recompiling php 4.3.1 without --with-mysql on the configure
line. Doing so did not remove the builtin 3.23.49 package.
You need to run configure with the new MySQL directory explicitly
specified, e.g.
./configure --with-mysql=/usr/local/mysql_4.1.7
HTH,
--
The directory mysql is a symbolic link to one of the other dirs.
If mysql points to old one rename it and make a new one:
mv mysql mysqlold
ls -s mysql-max-4.1.7-apple-darwin7.5.0-powerpc mysql
Do not remove
mysql-max-4.0.20-apple-darwin7.3.0-powerpc/data
it contains your old databases!!!
Santino
1 - 100 of 189 matches
Mail list logo
