MYSQL051 install problems

Discussions around the use of MySQL on VMS
Post Reply
User avatar
Posts: 13
Joined: Fri Oct 21, 2005 10:31 am
Location: London UK

MYSQL051 install problems

#1 Post by beaudoin_p »

I have also posted this to the VMS-MYSQL list:

I have managed to install MYSQL 051 successfully up to the point of running 'first_start' - I get this error:

InnoDB: Error: auto-extending data file /mysql051_root/data/ibdata1 is
of a different size
InnoDB: 640 pages (rounded down to MB) than specified in the .cnf file:
InnoDB: initial 6400 pages, max 0 (relevant if non-zero) pages!
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data files, and it failed here,
InnoDB: you should now edit innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB only wrote those files full of
InnoDB: zeros, but did not yet use them in any way. But be careful: do not
InnoDB: remove old data files which contain your precious data!
060812 16:53:51 [ERROR] Default storage engine (InnoDB) is not available
060812 16:53:51 [ERROR] Aborting

060812 16:53:51 [Note]
/DSA0/SYS20/SYSCOMMON/MYSQL051/VMS/BIN/mysqld.exe: Shutdown complete

%DELETE-W-SEARCHFAIL, error searching for
-RMS-E-FNF, file not found

I have not changed my.cnf - simply copied the template (with suggested security settings). I reviewed it but couldn't see any reason to modify it.

Is the line: Default storage engine (InnoDB) is not available the big clue? InnoDB should be available (assuming it is on default) and according to MY.CNF, it is the default engine used for create.

I assume it is trying to 'convert' the existing data from the older MYSQL here - that would be an unexpected bonus- I set up in such a way I can recreate the DB tables easily but then ran into a problem restoring the data:

I save the contents with MYSQL export statements and reload with MYSQL LOAD statements. This works in the older version just fine. ...
The LOAD statement produce errors (wrong size IIRC) and can't be restored under 051. In a pinch, I could re-format those statements into 'INSERT' statements easily enough (this works) but this is now getting a bit complicated. So, the original question: Have I somehow disallowed InnodDB tables?

Many thanks for any pointers


Post Reply