MySQL Bugs: #13896: Installation and configuration issues

Bug #13896	Installation and configuration issues
Submitted:	10 Oct 2005 12:53	Modified:	10 Oct 2005 15:12
Reporter:	sfx	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0	OS:	Windows (Windows XP Home)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

Description:
MySQL 5 appears not to allow InnoDB files to be stored in a different location to the installation path. Moreover, if MySQL 5 is installed on a different drive other than C:\Program Files\MySQL\... the Migration Toolkit will not load – perhaps because of the location of J2RE.

If, however, MySQL along with its tools are loaded into the same default location, then the MySQL service initiates without error and the Migration Toolkit will load, connect to a peripheral database and then subsequently reverse engineer.

This has been my experience after installing MySQL 5 along with its accompanying tools almost a dozen times... I really hope someone can investigate this. :(

How to repeat:
Try installing the InnoDB files to a different drive than where the MySQL default installation is found. This causes an error when the system attempts to start the MySQL service.

Also, try installing both MySQL and the Migration Toolkit to a different drive than the default location associated with the configuration wizard. This appears to prevent MT from loading. I am not sure, but this may have to do with the location of J2RE (I am using Java Runtime Environment 5 Update 5).

I was unable to repeat the behavior reported:

C:\mysql5013\bin>mysql -uroot
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1 to server version: 5.0.13-rc-nt

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> show variables like "%innodb%";
+---------------------------------+------------------------+
| Variable_name                   | Value                  |
+---------------------------------+------------------------+
| have_innodb                     | YES                    |
| innodb_additional_mem_pool_size | 2097152                |
| innodb_autoextend_increment     | 8                      |
| innodb_buffer_pool_awe_mem_mb   | 0                      |
| innodb_buffer_pool_size         | 8388608                |
| innodb_checksums                | ON                     |
| innodb_commit_concurrency       | 0                      |
| innodb_concurrency_tickets      | 500                    |
| innodb_data_file_path           | ibdata1:10M:autoextend |
| innodb_data_home_dir            | E:\MySQL Datafiles\    |
| innodb_doublewrite              | ON                     |
| innodb_fast_shutdown            | 1                      |
| innodb_file_io_threads          | 4                      |
| innodb_file_per_table           | OFF                    |
| innodb_flush_log_at_trx_commit  | 1                      |
| innodb_flush_method             |                        |
| innodb_force_recovery           | 0                      |
| innodb_lock_wait_timeout        | 50                     |
| innodb_locks_unsafe_for_binlog  | OFF                    |
| innodb_log_arch_dir             |                        |
| innodb_log_archive              | OFF                    |
| innodb_log_buffer_size          | 1048576                |
| innodb_log_file_size            | 10485760               |
| innodb_log_files_in_group       | 2                      |
| innodb_log_group_home_dir       | .\                     |
| innodb_max_dirty_pages_pct      | 90                     |
| innodb_max_purge_lag            | 0                      |
| innodb_mirrored_log_groups      | 1                      |
| innodb_open_files               | 300                    |
| innodb_support_xa               | ON                     |
| innodb_sync_spin_loops          | 20                     |
| innodb_table_locks              | ON                     |
| innodb_thread_concurrency       | 8                      |
| innodb_thread_sleep_delay       | 10000                  |
+---------------------------------+------------------------+
34 rows in set (0.22 sec)

mysql> show variables like "datadir";
+---------------+-------------------------------------------------------+
| Variable_name | Value                                                 |
+---------------+-------------------------------------------------------+
| datadir       | C:\Arquivos de programas\MySQL\MySQL Server 5.0\Data\ |
+---------------+-------------------------------------------------------+
1 row in set (0.00 sec)

mysql>

Notice that before to begin the install I was sure any InnoDB file already
exist on install directory due to older install process which weren't removed
during the uninstall process.