FW: Error 2003: Cannot connect to mySQL server on localhost <10061>

-----Original Message-----
From: Bob Melis [mailto:bobmelis@adelphia.net]
Sent: Friday, December 02, 2005 11:52 PM
To: myodbc@lists.mysql.com
Subject: RE: Error 2003: Cannot connect to mySQL server on localhost
<10061>


Success!! After doing the what I summarized below and restarting my
computer it now works as before with my java application. I forgot to
mention that I removed skip-bdb and skip-innodb from my.ini file.
Also,mysql created the ib_logfile0 the same size as ib_logfile1 which
I guess was needed. I alos but all my .frm files back before I
restarted my computer. The only thing I still need to do is see if I
can read/write to my DB via the CMD window.

Hopefully this will help anyone else that gets into is problem.

Bob


-----Original Message-----
From: Bob Melis [mailto:bobmelis@adelphia.net]
Sent: Friday, December 02, 2005 11:25 PM
To: myodbc@lists.mysql.com
Subject: RE: Error 2003: Cannot connect to mySQL server on localhost
<10061>


David, one more time. Maybe the following (Table mysql.host doesn't
exist.) can shed some light on how I might recover.

I went to mysql 15.6.1. Dealing with InnoDB Initialization Problems
and tried the following:

1. Deleted ibdata, ib_logfiles and .frm files (saved my data first in
another folder so I could retrieve it later).

2. Shut down mysql since it was running.

3. Started mysq at the CMD line with mysqld-nt --standalone and got
the following in my error log.

InnoDB: The first specified data file .\ibdata1 did not exist:
InnoDB: a new database to be created!
051202 21:58:22 InnoDB: Setting file .\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
051202 21:58:22 InnoDB: Log file .\ib_logfile0 did not exist: new to
be created
InnoDB: Setting log file .\ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
051202 21:58:23 InnoDB: Log file .\ib_logfile1 did not exist: new to
be created
InnoDB: Setting log file .\ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
051202 21:58:32 InnoDB: Started
051202 21:58:32 Fatal error: Can't open privilege tables: Table
'mysql.host' doesn't exist
051202 21:58:32 Aborting

051202 21:58:32 InnoDB: Starting shutdown...
051202 21:58:35 InnoDB: Shutdown completed
051202 21:58:35 mysqld-nt: Shutdown Complete

After initializing the files, InnoDB tried to start but had a Fatal
error. Is there any way to create Table mysql.host that does not exist
so it can open privilege tables? Do you think doing mysql_install_db
would help or would that screw things up, and it would be better to
download and reinstall from scratch?

Bob




-----Original Message-----
From: Bob Melis [mailto:bobmelis@adelphia.net]
Sent: Friday, December 02, 2005 7:18 PM
To: myodbc@lists.mysql.com
Cc: Armin Schoffmann [armin.schoeffmann@aegaeon.de]
Subject: RE: Error 2003: Cannot connect to mySQL server on localhost
<10061>


David, thanks soooo much.

You got my application running again with the skip innodb and bdb in
my.ini file. I will look into installing a later versions of mysql in
the future.

When you say save data files, that of course is the data files I
created. Do I need to save everything under the mysql\data directory
such as ibdata1, ib_logfile0, ib_arch_log_0000000000.

I assume I can reuse the mysql-connector-java file without downloading
it again. Is that correct?

Also, will I need to ...
- uninstall mysql before I download it, or
- just download and unzip it and it will automatically replace the
existing one?

Issue Resolved and thanks again.

Bob

-----Original Message-----
From: David Dindorp [mailto:ddi@dubex.dk]
Sent: Friday, December 02, 2005 5:31 AM
To: Bob Melis
Cc: myodbc@lists.mysql.com
Subject: RE: Error 2003: Cannot connect to mySQL server on localhost
<10061>


Bob Melis wrote:
> Below is my.ini file. I added skip innodb and
> bdb to get the mysqld-nt console to run.

> When I do the mysqld-nt --console, I get:
> ready for connections.

> Does this mean I will need to start mysql this way until
> I resolve the innodb issue or download mysql again?

No, if it starts OK in console mode with skip-innodb,
it _should_ run fine in service mode too (with skip-innodb).

> are there any advantages to upgrading

Use the MySQL feature comparison page:
http://dev.mysql.com/tech-resources/features.html

You might want to prod the MySQL folks and tell them to
update the web page to include MySQL series 5.

Also, you can read the MySQL change history:
http://dev.mysql.com/doc/refman/5.0/en/news.html

It only covers the currently recommended version.
For older versions, you'll have to dig out an
older version of the manual which it's included in:
http://dev.mysql.com/doc/refman/4.1/en/news.html

> I assume 5.0.16 would be used for larger
> applications then I am considering at this time.

No, it's equally suited for small applications.


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org