MySQL Bugs: #17672: Installation fail of mysql-5.0.18-win32 on Windows 2003

Bug #17672	Installation fail of mysql-5.0.18-win32 on Windows 2003
Submitted:	23 Feb 2006 14:27	Modified:	1 Mar 2006 13:01
Reporter:	Denis Lavoie	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0.18-win32	OS:	Windows (Windows 2003)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

Description:
I already have MySQL server 5.0.15-nt installed on my Windows Server 2003 machine and it works fine.  Now I really need to upgrade to version 5.0.18-nt to fix the problem 'MySQL Bugs #17655'.  When I try to install the version 5.0.18-nt on Windows Server 2003, I got an error that the system is not able to start the MySQL service.

Note: I installed the version 5.0.18-nt on my Windows XP machine and it works fine.  

How to repeat:
Execute 'setup.exe' from the file mysql-5.0.18-win32.zip on a Windows Server 2003 Enterprise Edition Service Pack 1 machine.

Choose the following options:
Setup type: Typical
Server type: Server Machine
Database usage: Multifunctional Database
Connection: Decision support
Enable TCP/IP: port number = 3306
Character set: Multilingualism
Check Install as Windows service: service name = MySQL

When I click on 'Execute' button to process the configuration, I got the following error:
- A red 'x' appear beside of Start Service
- An error message said 'Could not start the service MySQL.Error:0

Suggested fix:
I want to be able to install version 5.0.18-nt on Windows 2003!

In my event viewer, I got the following message:

"Default storage engine (InnoDB) is not available."

Thank you for the bug report.
Did you the upgrade selecting the same directory and existing older
version?
Anyway, open a command prompt screen and go to the \bin install
directory and then execute:

mysqld-nt --defaults-file=\path_install\my.ini --standalone --console

and show here the message errors.

Here is the result of the command you ask me:

C:\Program Files\MySQL\MySQL Server 5.0\bin>mysqld-nt --defaults-file="C:\Progra
m Files\MySQL\MySQL Server 5.0\my.ini" --standalone --console
InnoDB: The first specified data file C:\MySQL Datafiles\ibdata1 did not exist:
InnoDB: a new database to be created!
060223  9:57:08  InnoDB: Setting file C:\MySQL Datafiles\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Error: log file .\ib_logfile0 is of different size 0 46137344 bytes
InnoDB: than specified in the .cnf file 0 87031808 bytes!
060223  9:57:08 [ERROR] Default storage engine (InnoDB) is not available
060223  9:57:08 [ERROR] Aborting

060223  9:57:08 [Note] mysqld-nt: Shutdown complete

-------------------------

My previous database are stored in folder "C:\Program Files\MySQL\MySQL Server 5.0\data"

I did the upgrade in the same directory than the existing older version...  However, after the first unsuccessfull installation, I tried to uninstall the previous version and reinstall the new one and so on...  I always tried to install MySQL server on the same directory.  I got always the same problem.

Thanks for your support, 

Denis Lavoie

The error messages means that you installed over the older version
and with different InnoDB's ib_logfile0 file, then the workaround is
to edit the my.ini file with the correct size, so go the \data directory
see the file size and edit the my.ini with notepad.

Hi Miguel, 

Here is now the error message I got:  (this is only the last part of the message because the message is too long.  There is many 000000000000000 like dump data)

                                                      ;InnoDB: End of page dump
060223 10:52:07  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum
 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
060223 10:52:07 [ERROR] mysqld-nt: Got signal 11. Aborting!

060223 10:52:07 [ERROR] Aborting

060223 10:52:07 [Note] mysqld-nt: Shutdown complete

For the procedures you did and if you don't have backup of the
older installation I guess you lost all the data and now is only
possible to make a full fresh install, if it is the case are you
have on hands, then my suggestion is to remove the installation
using the control panel add/remove option. Then go to the install
path and delete the whole directory and try a fresh install again.

If I made a backup of the data directory only, is it possible to reinstall the my previous version 5.0.15 from scratch and overwrite the data directory with the one I backed up?

Is there any ways to retreive my old database if I only take the data directory in backup?

Thanks for your help, 

Denis Lavoie

If you have the data directory and IF YOU HAVE DEFINED in previous
install in the same directory the InnoDB's files then you can recover
all the data.
Do a fresh install, make sure you select the same options for to create
the InnoDB files (that was the reason of the whole issue) or you can
edit the my.ini file created with the correct InnoDB files size. Then you 
replace the data directory for the backup.

Now I reinstalled the old version 5.0.15 the exact same way I did before, in the same directory.  I change file size of the InnoDB log file in My.ini file and I copy my backup data directory into the fresh install.  Now I get this error messages... Help please....

C:\Program Files\MySQL\MySQL Server 5.0\bin>mysqld-nt --defaults-file="C:\Progra
m Files\MySQL\MySQL Server 5.0\my.ini" --standalone --console
060223 13:49:17  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
060223 13:49:17  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 1812839167.
InnoDB: Doing recovery: scanned up to log sequence number 0 1812839167
InnoDB: Page directory corruption: supremum not pointed to
060223 13:49:18  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 0000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
...
...
                                                      ;InnoDB: End of page dump
060223 13:56:28  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum
 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page directory corruption: supremum not pointed to
060223 13:56:28  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 0000000000000000000000000000000000000000000000000000000000000000
...
...
                                                      ;InnoDB: End of page dump
060223 13:57:11  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum
 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
060223 13:57:11 [ERROR] mysqld-nt: Got signal 11. Aborting!

060223 13:57:11 [ERROR] Aborting

060223 13:57:11 [Note] mysqld-nt: Shutdown complete

Any other idea before I loose my data forever?

Denis Lavoie

Well un-install the 5.0.18 version, do an install of the older version
and use the data backup in the same way. If you able for to start
the server then do a dump file using mysqldump for to be loaded
when you install a 5.0.18 server.

I did not be able to restore my database.  I took an old backup and start from scratch the installation of the server.  Now everything work fine.

The log file size problem is Bug#13494.