SEO

Hi,
I'm upgrading from 4.1.11 to 5.0.51. I have a complication in that we
have two instances of mysql running on one server and this is the
upgrade to one instance and not the other. The software is not
installed in the default location; the tar.gz file was unzipped under
the /opt/mysql/dev/ directory, then a link was created for "5.0".
We're using ports 3306 & 3307. The upgrade was run on the instance
that uses 3307. I have made the necessary changes to my.cnf and the
server is now running. Am trying to run mysql_upgrade as follows
(from the bin directory):
../mysql_upgrade --basedir=/opt/mysql/dev/5.0 --datadir=/ua01/mysqldata/
dev -u root -p --port=3307 --socket=/tmp/mysqldev.sock --verbose > /
opt/mysql/dev/mysqlupgrade_dev.txt

I get the following message:
/opt/mysql/dev/mysql-5.0.51a-linux-i686-glibc23/bin/mysqlcheck: Got
error: 1064: You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to
use near 'FOR UPGRADE' at line 1 when executing 'CHECK TABLE ... FOR
UPGRADE'.

Please help. I've tried all sorts of variations on the command above
but I can't get it to work and I can't find anything about this in the
manual.

I'll be very grateful for any help you can provide.

Sarah Anderson

Sarah wrote:
> Hi,
> I'm upgrading from 4.1.11 to 5.0.51. I have a complication in that we
> have two instances of mysql running on one server and this is the
> upgrade to one instance and not the other. The software is not
> installed in the default location; the tar.gz file was unzipped under
> the /opt/mysql/dev/ directory, then a link was created for "5.0".
> We're using ports 3306 & 3307. The upgrade was run on the instance
> that uses 3307. I have made the necessary changes to my.cnf and the
> server is now running. Am trying to run mysql_upgrade as follows
> (from the bin directory):
> ./mysql_upgrade --basedir=/opt/mysql/dev/5.0 --datadir=/ua01/mysqldata/
> dev -u root -p --port=3307 --socket=/tmp/mysqldev.sock --verbose > /
> opt/mysql/dev/mysqlupgrade_dev.txt
>
> I get the following message:
> /opt/mysql/dev/mysql-5.0.51a-linux-i686-glibc23/bin/mysqlcheck: Got
> error: 1064: You have an error in your SQL syntax; check the manual
> that corresponds to your MySQL server version for the right syntax to
> use near 'FOR UPGRADE' at line 1 when executing 'CHECK TABLE ... FOR
> UPGRADE'.
>
> Please help. I've tried all sorts of variations on the command above
> but I can't get it to work and I can't find anything about this in the
> manual.
>
> I'll be very grateful for any help you can provide.
>
> Sarah Anderson
>


--socket=/tmp/mysqldev.sock

Are you sure this is the correct socket for the upgraded instance?

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

On Mar 14, 11:32 pm, Jerry Stuckle <jstuck...@attglobal.net> wrote:
>
> --socket=/tmp/mysqldev.sock
>
> Are you sure this is the correct socket for the upgraded instance?
>


Hi Jerry,

Thanks for answering! Yes, this instance is on port 3307 and uses
that socket.

Sarah

Sarah wrote:
> On Mar 14, 11:32 pm, Jerry Stuckle <jstuck...@attglobal.net> wrote:
>> --socket=/tmp/mysqldev.sock
>>
>> Are you sure this is the correct socket for the upgraded instance?
>>
>
>
> Hi Jerry,
>
> Thanks for answering! Yes, this instance is on port 3307 and uses
> that socket.
>
> Sarah
>

A connection will use either a port or a socket - not both. But the
reason I asked is this is typical of trying to run the script against a
system which has not been upgraded. I take it you have stopped and
restarted the server?

What happens if you connect to the socket with mysql and do a SHOW STATUS?

Or, maybe easier - what happens if you stop the non-upgraded system and
try to run the script?

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

On Mar 16, 11:58 am, Jerry Stuckle <jstuck...@attglobal.net> wrote:
> Sarah wrote:
> > On Mar 14, 11:32 pm, Jerry Stuckle <jstuck...@attglobal.net> wrote:
> >> --socket=/tmp/mysqldev.sock
>
> >> Are you sure this is the correct socket for the upgraded instance?
>
> > Hi Jerry,
>
> > Thanks for answering! Yes, this instance is on port 3307 and uses
> > that socket.
>
> > Sarah
>
> A connection will use either a port or a socket - not both. But the
> reason I asked is this is typical of trying to run the script against a
> system which has not been upgraded. I take it you have stopped and
> restarted the server?
>
> What happens if you connect to the socket with mysql and do a SHOW STATUS?
>
> Or, maybe easier - what happens if you stop the non-upgraded system and
> try to run the script?
>
> --
> ==================
> Remove the "x" from my email address
> Jerry Stuckle
> JDS Computer Training Corp.
> jstuck...@attglobal.net
> ==================

Hi Jerry,

Thanks again for your response. I figured out the problem. There's a
reference in the PATH variable to another instance of 4.1.11 which is
what mysql used to startup - stupid me, I thought it was starting the
upgraded version. Anyway, I've got it running correctly on the
upgraded version now and once I did that I was able to run the
mysql_upgrade program. Hooray! Thanks again for helping me, I really
appreciate it.

Sarah Anderson