At 01:33 2/12/2005, Bob Melis wrote:
Hello,
Please next time use our bug database for to report issue like
this, internal is for other purposes.
>My .err says I cannot initiate mysql Databases since I reinstalled
>windows xp. I've been working with folks on the myodbc list and they
>sent me to this list since they think it is an internal problem. When
>I run mysql as a standalone console by adding skip-innodb and skip-bdb
>to my.ini file, I can get it running. But when it trys to run at
>windows startup, it shuts down. It was working properly before I
>reinstalled windows xp. I am using version 4.0.13 with
>mysql-connector-java-3.0.8.
The above sounds like InnoDB found the data and log files with size
different than it try to start, for example you created the existing
ones different values than the default or vice-versa.
Start the server from a command prompt:
mysqld-nt --standalone --console
and take a look in the error message.
>History: When I noticed this problem, after reinstalling windows xp, I
>got Error 2003 and could not get mysql to run at windows startup as it
>did in the past. I noticed that my winmysqladmin said it could not
>find myodbc driver 3.51. Next I downloaded it using the Windows ODBC
>Data Source Administrator but the test was in error. I guess that is
>because mysql was not running. When I got mysql running as a
>standalone console the windows odbc data source admin test worked but
>the the winmysqladmin still said myodbc not found while my databases
>showed up.
The above is a wrong message since the registry value which winmysqladmin
tries to search aren't used anymore. That tool is deprecated.
>Is there some way I can get it to run again without reinstalling
>mysql? I assume something is not working between it and windows.
>
>Bob
>
>
>
>--
>MySQL Internals Mailing List
>For list archives: http://lists.mysql.com/internals
>To unsubscribe: http://lists.mysql.com/internals?unsub=1
Regards,
Miguel Angel Solórzano <miguel@stripped>
Florianopolis Santa Catarina - Brazil