On Fri, May 15, 2015 at 8:27 PM, Reindl Harald wrote:
>
> Am 15.05.2015 um 23:27 schrieb Larry Martell:
>>
>> 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 fro
Am 15.05.2015 um 23:27 schrieb Larry Martell:
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 MyS
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
On Sun, Apr 4, 2010 at 9: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.
> Of course what Rob says
Be aware that if it is an unpatched version of 5.0.77, then there is
a bug related to name_const (http://bugs.mysql.com/bug.php?id=42014)
that can cause serious problems (infinite server crashes if it
happens in a replication thread). Redhat/CentOS have applied the
patch, but other sources
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 fi
On Tue, Mar 30, 2010 at 6:36 AM, Marco Baiguera
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 os is CentOS rele
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,
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
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 :)
I already posted about this:
http://lists.mysql.com/mysql/215100
or google for "moving from 3.23.58 to 5.0.45"
I never recommend to install mysql as default package, is way too limiting.
I manage to have as many mysql installations on the same server as the
hardware can carry,
but not software
Hi,
I don't know what Linux distro you're using, but I'd make a backup of
/var/lib/mysql dir before you do anything (in case the mysql package
decides to nuke your stuff). If you have a dump of your dbs, that's fine
too. And maybe a backup of your my.cnf.
Just install the new mysql package,
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/
>
>
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 of My
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
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
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, you
>-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
>
&g
MySQL
Support * Consulting * Administration
http://www.olindata.com
On Wed, Feb 25, 2009 at 11:00 PM, Jerry Schwartz
wrote:
>
>
> From: Gary W. Smith [mailto:g...@primeexalia.com]
> Sent: Wednesday, February 25, 2009 4:36 PM
> To: Claudio Nanni; Jerry Schwartz
> Cc: MySql
>
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
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.
but
some lib issues with the older CentOS.
Gary
From: Claudio Nanni [mailto:claudio.na...@gmail.com]
Sent: Wed 2/25/2009 12:50 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
Hi Jerry,
probably does not help you very much and excuse me in advance for this,
but there is little use in having a development/preproduction system on
different architecture,
none of the issues you faced with windows (services installation probably)
will show up on a CentOS box.
In particular an
Use mysqldump on the old version and import the data into new version in my
opinion.
On Fri, Aug 22, 2008 at 1:29 AM, Andy Shellam <[EMAIL PROTECTED]>wrote:
> FYI the manual for 5.0 recommends upgrading to 4.1 first.
>
> "As a general rule, we recommend that when upgrading from one release
> seri
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 u
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, but don
In the last episode (Oct 23), Ivan Longhi said:
> I'm running mysql-server on a linux debian box
>
> with apt package system I upgraded mysql server from 4.1 to 5.0 (apt
> automatically execute mysql_upgrade)
>
> now on my 5.0.32 server almost everything works fine, except for a
> database cont
Hi David,
> Go from 4.1 to 5.0 to 5.1 . This is safer.
Thanks for the advise, I'll plan this route.
I still have the problem that 5.1 has no 'mysql_upgrade' program.
I would really be interested in hearing from somebody from MySQL. Does
this version need no upgrading? I am confused...
R
Hi David,
> Go from 4.1 to 5.0 to 5.1 . This is safer.
Thanks for the advise, I'll plan this route.
I still have the problem that 5.1 has no 'mysql_upgrade' program.
I would really be interested in hearing from somebody from MySQL. Does
this version need no upgrading? I am confused...
R
On Mon, Oct 23, 2006 at 01:49:14PM +0100, Ben Clewett wrote:
> MySQL,
>
> I am trying to upgrade from 4.1 to 5.1.
>
> Your manual states I should run mysql_upgrade.
>
> But there is no such program in our pre-compiled binary, only a man page!
>
> $ find . -name "mysql_upgrade*"
> ./mysql-5.1.11
On 7/18/06, Duncan Hill <[EMAIL PROTECTED]> wrote:
On Tuesday 18 July 2006 16:08, Dominik Klein wrote:
> > My question is : do I have to follow the upgrade procedure from 4.0 to
> > 4.1 or can I juste installed the new binaries? We are not ready yet for
> > the version 5.
>
> As always when upgra
On Tuesday 18 July 2006 16:08, Dominik Klein wrote:
> > My question is : do I have to follow the upgrade procedure from 4.0 to
> > 4.1 or can I juste installed the new binaries? We are not ready yet for
> > the version 5.
>
> As always when upgrading: Make sure you have a backup :)
This becomes a
My question is : do I have to follow the upgrade procedure from 4.0 to
4.1 or can I juste installed the new binaries? We are not ready yet for
the version 5.
As always when upgrading: Make sure you have a backup :)
Then install the new version and move (copy if you have the space) the
data-dir
On 3/3/06, Claire Lee <[EMAIL PROTECTED]> wrote:
> Hello,
> I'm going to upgrade from 4.1 to 5.0. My question is
> how do I handle the data from old version. Do I need
> to recreate tables in the mysql database when I
> install the new version or can I use the old mysql
> database from the old vers
Hello.
Most probably you have to upgrade when you need one of the new features
of MySQL 5.0. See:
http://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-nutshell.html
suomi wrote:
> Hi listers
> i have been looking around quite a bit for info on
> - when do i need to upgrade to mysql 5.x (because su
Jon Miller wrote:
Jon,
I'm currently running MySQL on RedHat 7.2 and now I'm in the processing of
finishing testing a new server which has SUSE Linux Enterprise Server 9.
My question is my database currently resides on RH7.2 and
MySQL-server-4.0.13-0. I want to install the latest version on
Hello.
> we would like to upgrade to 4.1.15, which I believe is the current
> stable release,
5.0.15 is stable as well, and, in my opinion, it is better to upgrade
to it (though 4.1.15 of course). Bug database might be helpful to
find some RH related issues:
http://bugs.mysql.com
Hello.
MySQL AB recommends a gradual upgrade. See:
http://dev.mysql.com/doc/refman/4.1/en/upgrade.html
http://dev.mysql.com/doc/refman/5.0/en/upgrade.html
Cedric Gavage wrote:
> Hi all,
>
> A little question...
>
> Can I upgrade directly a server with MySQL 3.23.x version whi
Hello.
>except for shared-compat, for which there is only a 4.1.13 version - is it
>acceptable that that RPM be a rev back from the rest?
In my opinion, this rpm contains only old libraries which don't change
with every new release of MySQL. However,I'm agree - it's a bit
confusing.
>o
> Osvaldo Sommer
>
> -Original Message-
> From: Nuno Pereira [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 01, 2005 7:38 AM
> To: Osvaldo Sommer
> Cc: mysql@lists.mysql.com
> Subject: Re: Upgrade from 4.0.12 to 4.0.25
>
> Osvaldo Sommer wro
Thanks, but that link is for 4.1.x and not for 4.0.x
Osvaldo Sommer
-Original Message-
From: Nuno Pereira [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 01, 2005 7:38 AM
To: Osvaldo Sommer
Cc: mysql@lists.mysql.com
Subject: Re: Upgrade from 4.0.12 to 4.0.25
Osvaldo Sommer wrote
Osvaldo Sommer wrote:
Hi List
I look up on the online manual for directions for this kind of upgrade
but i found nothing.
Is there something I have to do extra or the upgrade so smoth?
Osvaldo Sommer
See http://lists.mysql.com/mysql/186726
--
Nuno Pereira
--
MySQL General Mailing List
Fo
--- Jeff Lacki <[EMAIL PROTECTED]> wrote:
>
+-+--+--+-++---+
> | Field | Type | Null | Key |
> Default| Extra |
>
+-+--+--+-++---+
> | id | bigint(20) |
lack of a primary key was the problem.
I am surprised the problem didnt show up in 3.23
but did in 4.12
Thanks for the suggestions!
Jeff
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Jeff Lacki wrote:
Ok I appear to have narrowed down the issue.
it appears to be the last table I had listed
named 'user_account1':
mysql> describe user_account1;
+-+--+--+-++---+
| Field | Type | Null | Key | Default| Ext
Ok I appear to have narrowed down the issue.
it appears to be the last table I had listed
named 'user_account1':
mysql> describe user_account1;
+-+--+--+-++---+
| Field | Type | Null | Key | Default| Extra |
+--
Im running a 2.8Ghz celeron P4, 1Gbyte RAM on
a 160Gb HD (IDE).
mysql> show variables;
+-++
| Variable_name | Value
|
+--
Hello.
Maybe you had configuration file with different
settings. Nevertheless, send the information about
your RAM size, the output of SHOW VARIABLES,
configuration file, table definitions (use SHOW CREATE
TABLE), EXPLAIN output for your query, and list should
help you.
Jeff Lacki <[EM
Are you running the stock Apple MySQL install??
I went through this a few times. If so figure out where the default
Apple install places the data dir.
The MySQL pkg installers will install everything in:
/usr/local/mysql/data/
where:
/usr/local/mysql/
is really a symbolic link to each in
Hello.
See:
http://dev.mysql.com/doc/mysql/en/upgrade.html
m i l e s <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a silly questionDUH
>
> Im running OS X Server, I installed 4.018 and I want to run 4.1.13,
> how do I upgrade the server, without losing anything ?
>
> D
Hassan Schroeder wrote:
mm wrote:
There is a lot a pain here.
I downloaded the rpm packages
that's where the pain starts :-)
If you're trying to run multiple versions of MySQL for pre-migration
testing (or whatever), *don't use rpms* -- get the tar file of the
binary, and just untar it as
mm wrote:
There is a lot a pain here.
I downloaded the rpm packages
that's where the pain starts :-)
If you're trying to run multiple versions of MySQL for pre-migration
testing (or whatever), *don't use rpms* -- get the tar file of the
binary, and just untar it as /usr/local/mysql-4.1.12 or
Selon mm <[EMAIL PROTECTED]>:
> Hi,
> There is a lot a pain here.
> I downloaded the rpm packages
> MySQL-server-4.1.12-1.i386.rpm
> MySQL-shared-4.1.12-1.i386.rpm
> MySQL-bench-4.1.12-1.i386.rpm
> MySQL-shared-compat-4.1.11-0.i386.rpm
> MySQL-client-4.1.12-1.i386.rpm
> MyS
Hi,
There is a lot a pain here.
I downloaded the rpm packages
MySQL-server-4.1.12-1.i386.rpm
MySQL-shared-4.1.12-1.i386.rpm
MySQL-bench-4.1.12-1.i386.rpm
MySQL-shared-compat-4.1.11-0.i386.rpm
MySQL-client-4.1.12-1.i386.rpm
MySQL-devel-4.1.12-1.i386.rpm
MySQL-embedded-
Hello.
Read:
http://dev.mysql.com/doc/mysql/en/upgrade.html
http://dev.mysql.com/doc/mysql/en/multiple-servers.html
And search in archives about possible troubleshooting:
http://lists.mysql.com/mysql/
mm <[EMAIL PROTECTED]> wrote:
>
> I have on my system, Fedora core
Yes You can have both versions, infact this is the preferred way to
upgrade, but the only thing is that have the new version install in
/usr/local/mysql2/ or what ever you want and change the port that the
newer daemon listens on instead of the default 3306, here's a good
link from the doc's of mys
Hello.
The problem may in that as of MySQL 5.0.3, it is necessary to have the
EXECUTE privilege to be able to execute the routine. I think you should
grant an EXECUTE privilege to other users. See:
http://dev.mysql.com/doc/mysql/en/create-procedure.html
http://dev.mysql.com/doc/mysql
> Does Debian package preserve a master.info and relay-log.info files?
I'll check with some Debian experts.
> Do you stop slave before the upgrade?
No.
> What does the 'SHOW SLAVE STATUS'
> statement report?
Before that everything is ok, after I don't know now that it is
running ok, but I'll
Hello.
Does Debian package preserve a master.info and relay-log.info files?
Do you stop slave before the upgrade? What does the 'SHOW SLAVE STATUS'
statement report?
Jacob Friis Larsen <[EMAIL PROTECTED]> wrote:
> I use Debian Sarge as my Linux distribution on two servers who replicate
Hello.
See:
http://dev.mysql.com/doc/mysql/en/upgrade.html
http://dev.mysql.com/doc/mysql/en/windows-upgrading.html
If your MySQL distribution came as embedded version, you should look at:
http://dev.mysql.com/doc/mysql/en/libmysqld-overview.html
The complete answers related to
Mattias,
- Original Message -
From: "Mattias J" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Friday, January 14, 2005 8:50 PM
Subject: Re: Upgrade correpted InnoDB tables
At 2005-01-14 18:09, you wrote:
this is very strange. Have you used MySQL-5.0.x
"Mattias J" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, January 13, 2005 6:57 PM
Subject: Re: Upgrade correpted InnoDB tables
There are mostly just 2 or 3 corrupted tables out of about 100 in each
database/schema/namespace and if possible we would like to k
Mattias,
was it so that you RECREATED those tables with 4.0.21, and you STILL got the
error in 4.1.8?
Regards,
Heikki
- Original Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To:
Sent: Friday, January 14, 2005 7:02 PM
Subject: Re: Upgrade correpted InnoDB tables
iday, January 14, 2005 4:39 PM
Subject: Re: Upgrade correpted InnoDB tables
Ok. This is what happened:
We removed MySQL from the server and re-installed 4.0(.21) then put back
some old data.
When trying to upgrade to 4.1.9 we encountered the same problem, with the
exact same tables being corrupted
/InnoDB_Monitor.html
Regards,
Heikki
- Original Message - From: "Mattias J" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, January 13, 2005 6:57 PM
Subject: Re: Upgrade correpted InnoDB tables
There are mostly just 2 or 3 corrupted tables out of about 100
c
Sent: Thursday, January 13, 2005 6:57 PM
Subject: Re: Upgrade correpted InnoDB tables
There are mostly just 2 or 3 corrupted tables out of about 100 in each
database/schema/namespace and if possible we would like to keep the
information in the other tables.
At 2005-01-13 17:47, you wrote:
If you don&#x
InnoDB which also backs up MyISAM
tables
http://www.innodb.com/order.php
- Original Message -
From: "Mattias J" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, January 13, 2005 6:57 PM
Subject: Re: Upgrade correpted InnoDB tables
There are mo
There are mostly just 2 or 3 corrupted tables out of about 100 in each
database/schema/namespace and if possible we would like to keep the
information in the other tables.
At 2005-01-13 17:47, you wrote:
If you don't have any data in innodb, delete and recreate the
tablespace including the frm f
If you don't have any data in innodb, delete and recreate the
tablespace including the frm files. This will give you a fresh 4.1
table space to import into.
-Eric
On Thu, 13 Jan 2005 16:37:39 +0100, Mattias J <[EMAIL PROTECTED]> wrote:
> Earlier today we tried upgrading one of our MySQL servers
Yes.I know that 3 -> 4.0 -> 4.1 is the recommended way but It will cost a lot of
downtime. So I decided to do 3->4.1 way.
The part that I am not quite sure is the converting the database. Why it is
needed? If I just copy the old db and run the 4.1?
I 've not found clear explination in the docs.
I'v
Hmmm, found the problem. In previous versions the installer did not delete
and write over existing tables in the mysql database. Good thing I had the
database backed up. Be careful all...
Fredrick
- Original Message -
From: "Fredrick Bartlett" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]
On Tuesday 30 November 2004 04:44 pm, Greg Macek wrote:
> OK, sounds like what I should do is the following:
>
> * Upgrade current mysql install (3.23.49) to latest stable 4.0 series
> (4.0.22 according to the website)
> * Test out all applications and make sure everything is working as
> expected
On Tue, 2004-11-30 at 11:50 -0600, Jeff Smelser wrote:
> On Monday 29 November 2004 11:35 pm, Greg Macek wrote:
> > I was thinking about this as well, but was hoping to minimize the amount
> > of work I would have to do. However, if this makes the most sense for
> > upgrading, perhaps this is what
On Monday 29 November 2004 11:35 pm, Greg Macek wrote:
> I was thinking about this as well, but was hoping to minimize the amount
> of work I would have to do. However, if this makes the most sense for
> upgrading, perhaps this is what I'll do.
Actually, I think you will be minimizing going the 4.
On Mon, 2004-11-29 at 13:11 -0600, Paul DuBois wrote:
> At 12:57 -0600 11/29/04, Jeff Smelser wrote:
> >On Monday 29 November 2004 09:01 am, Greg Macek wrote:
> >
> >> I am actually in the process of planning a similar upgrade for our
> >> database server. None of our databases are that big, but
At 12:57 -0600 11/29/04, Jeff Smelser wrote:
On Monday 29 November 2004 09:01 am, Greg Macek wrote:
I am actually in the process of planning a similar upgrade for our
database server. None of our databases are that big, but was wondering
about what "gotcha's" I should be on the lookout for. I pl
On Monday 29 November 2004 09:01 am, Greg Macek wrote:
> I am actually in the process of planning a similar upgrade for our
> database server. None of our databases are that big, but was wondering
> about what "gotcha's" I should be on the lookout for. I planned on
> walking through the upgrade pa
On Wed, 2004-11-24 at 09:15 -0600, Jeff Smelser wrote:
> On Wednesday 24 November 2004 07:32 am, Hristo Chernev wrote:
> > How to upgrade from 3.23.58 to 4.1.7? Which is the easiest way with minimal
> > risk and downtime?
>
> Yeah right.. ;)
>
> > Background: Heavy loaded mysql server, only one
On Wednesday 24 November 2004 07:32 am, Hristo Chernev wrote:
> How to upgrade from 3.23.58 to 4.1.7? Which is the easiest way with minimal
> risk and downtime?
Yeah right.. ;)
> Background: Heavy loaded mysql server, only one database but it is huge -
> 5GB.The database is replicated to another
Read thru the changelog online and see if there's any fixes that
affect you or new features you want.. otherwise just leave it..I
have some terribly old mysql versions running, but they are rock solid
doing their job.. "If it aint broke don't fix it?" might apply...
On Mon, 22 Nov 2004 21:3
I'm referring to the MySql server v.4.1.5 that I'm using now, as
compared to the newer release of v.4.1.7
Paul DuBois wrote:
At 20:09 -0700 11/22/04, Steve Grosz wrote:
I'm using 4.15 currently, and it seems to be very stable. I noticed
that a v4.17 or something has come out recently.
Versions
At 20:09 -0700 11/22/04, Steve Grosz wrote:
I'm using 4.15 currently, and it seems to be very stable. I noticed
that a v4.17 or something has come out recently.
Versions 4.15 and 4.17 of what? You're asking us whether it's worth
upgrading without specifying what it is you're asking about?
Do you
Hi.
> First, how can I detect, on localhost, which port MySQL is using?
Look at my.cnf.
Also see:
http://dev.mysql.com/doc/mysql/en/Can_not_connect_to_server.html
Schalk Neethling <[EMAIL PROTECTED]> wrote:
> Since installing the latest 4.1 version of MySQL I have not been able to
On 4 Nov 2004 at 0:59, Schalk Neethling wrote:
> Since installing the latest 4.1 version of MySQL I have not been able to
> run phpMyAdmin.
>
> I have since gathered that the current version of phpMyAdmin is not
> compatible. I therefore ran Add/Remove programs on Windows and installed
> 4.0.2
Sebastien,
please consult
http://dev.mysql.com/doc/mysql/en/Upgrading-from-4.0.html.
For InnoDB, the following is the most important upgrade note:
"
Upgrading: If you have stored characters < ASCII(32) to non-latin1
non-BINARY indexed columns in MySQL versions <= 4.1.2, then you have to
rebuild t
- Original Message -
From: "Schalk Neethling" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 03, 2004 5:59 PM
Subject: Upgrade - Downgrade problems
> Since installing the latest 4.1 version of MySQL I have not been able to
> run phpMyAdmin.
>
> I have since gather
Haitao,
are you using MyISAM or InnoDB tables?
There were only two weeks between the 4.1.6 and 4.1.7 releases, and
filesort.cc was not modified at all in that time. The error 'Sort aborted'
comes if the sort function fails for some reason.
Can you find out what query is causing these errors?
Bes
Dear Victor Pendleton:
It contains both isam & innodb tables.
At 2004-07-14, 12:29:39 you wrote:
What table types are you currently using?
-Original Message-
From: MaFai
To: [EMAIL PROTECTED]
Sent: 7/13/04 10:09 PM
Subject: Upgrade 3.23 to 4.1.x
Dear all:
Do any on
Okay, so what I did to solve this was:
ln -s /var/lib/mysql/mysql.sock /tmp/mysql.sock
That seems like a bit of a hack though. The my.cnf file has this line:
socket=/var/lib/mysql/mysql.sock
Anyone know why it's looking in /etc ?
On Jul 14, 2004, at 4:53 PM, Jough P wrote:
Greetings all,
I recentl
The correct way to deal with this is to edit /etc/my.cnf and, in the
mysqld section set the location of the socket.
[mysqld]
socket = /tmp/mysql.sock
if there are other systems expecting it to be at the new location, a
simple end run might be to create a link at /tmp/mysql.sock ->
/var/lib/mysq
What table types are you currently using?
-Original Message-
From: MaFai
To: [EMAIL PROTECTED]
Sent: 7/13/04 10:09 PM
Subject: Upgrade 3.23 to 4.1.x
Dear all:
Do any one try to upgrade the mysql from 3.23 to 4.1?
In doc,mysql doesn't recommend update the mysql from diff series.Do any
on
rpm -qa|grep mysql will show you what mysql
packages you have installed.
You probably have both 3.x and 4.x packages installed
and assuming you don't have a 3.x database you want to
preserve, I would suggest uninstalling the 3.x package
with rpm --erase name_of_3.x_package
To determine where the
Am Tuesday 01 June 2004 16:54 schrieb Larry Lowry:
> I'm running 4.1.1 on RH 9. I want to upgrade this
> to 4.1.2. I'm using the rpm from the MySQL site.
>
> If I just try to install it with rpm -i then I get a bunch
> of errors about conflicting files from the 4.1.1-1
> install. If I try to un
PROTECTED]>
Sent: Tuesday, June 01, 2004 8:01 AM
Subject: Re: Upgrade 4.1.1 to 4.1.2
> Man rpm and read a bit about the *upgrade* option...
>
> rpm -Uvh name-of-package
>
>
> Larry Lowry wrote:
> > I'm running 4.1.1 on RH 9. I want to upgrade this
> > to
Rpm -U xxx
> -Original Message-
> From: Larry Lowry [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 01, 2004 9:55 AM
> To: [EMAIL PROTECTED]
> Subject: Upgrade 4.1.1 to 4.1.2
>
> I'm running 4.1.1 on RH 9. I want to upgrade this
> to 4.1.2. I'm using the rpm from the MySQL site
Man rpm and read a bit about the *upgrade* option...
rpm -Uvh name-of-package
Larry Lowry wrote:
I'm running 4.1.1 on RH 9. I want to upgrade this
to 4.1.2. I'm using the rpm from the MySQL site.
If I just try to install it with rpm -i then I get a bunch
of errors about conflicting files from th
"Duke, Brian" <[EMAIL PROTECTED]> wrote:
>
> I needed to do some subqueries. I had mysql-3.23. Somehow I thought
> mysql4 included subqueries. Loaded mysql-4.0. Converted everything and
> got it working except it doesn't do subqueries. Therefore we installed
> mysql-4.1.1 6 hours of figuring out t
I needed to do some subqueries. I had mysql-3.23. Somehow I thought
mysql4 included subqueries. Loaded mysql-4.0. Converted everything and
got it working except it doesn't do subqueries. Therefore we installed
mysql-4.1.1 6 hours of figuring out the permissions finally we got the
databases all fix
> I have Mysql 4.0.13 installed. I need to know if upgrading is an option
> or if installing the latest binary is a better option.
>
> To be more candid, I have finished the install with the following
> config. Not so much content yet...Just some pictures that can be
> uploaded again.
>
> Windows
"David B. Held" <[EMAIL PROTECTED]> wrote:
> "Egor Egorov" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>> [...]
>> Do you lose all your databases and tables or tables of
>> the database 'mysql'? Do you have databases
>> directories and files of tables in these dirs?
>
> Never min
1 - 100 of 148 matches
Mail list logo
