0006307: Upgrade from 1.0.0a2 to 1.0.0rc2 fails trying to create mantis_config_table which already exists - MantisBT - Signup temporarily disabled due to spam

ID	Project	Category	View Status	Date Submitted	Last Update

0006307	mantisbt	upgrade	public	2005-09-30 17:02	2007-08-02 02:31

Reporter	gtomlin	Assigned To	grangeway
Priority	normal	Severity	block	Reproducibility	always
Status	closed	Resolution	no change required
Product Version	1.0.0rc2

Summary	0006307: Upgrade from 1.0.0a2 to 1.0.0rc2 fails trying to create mantis_config_table which already exists
Description	Running admin\install.php as directed by: http://manual.mantisbt.org/manual.installation.upgrading.php Create database if it does not exist GOOD Attempting to connect to database as user GOOD Create Schema ( CreateTableSQL on mantis_config_table ) BAD CREATE TABLE mantis_config_table ( config_id VARCHAR(64) NOT NULL, project_id INTEGER NOT NULL DEFAULT 0, user_id INTEGER NOT NULL DEFAULT 0, access_reqd INTEGER DEFAULT 0, type INTEGER DEFAULT 90, value TEXT NOT NULL, PRIMARY KEY (config_id, project_id, user_id) )TYPE=MyISAM Table 'mantis_config_table' already exists
Additional Information	Environment: Win XP SP1 Apache 2.0.39 PHP 4.2.2 dev MySQL 4.0.20a-nt Using MySQL root id for both usernames on install.php Firefox 1.0.7
Tags	No tags attached.

gtomlin 2005-10-03 11:49 reporter ~0011463	It turns out that if you go through admin/index.php and run through the upgrades in admin/upgrade.php, install.php succeeds. However, this is contrary to the advice of step 6 of http://manual.mantisbt.org/manual.installation.upgrading.php. This procedure instructs the user to go directly to admin/install.php unless the user is migrating from pre-1.0.0. My database was created using 1.0.0a2, so according to the instructions I should not have run admin/upgrade.php. The instructions should be fixed to reflect current reality.

thraxisp 2005-10-04 22:10 reporter ~0011466	There are two sections for upgrading. For new installations, you use the new installer (install.php). To upgrade an older installation to 1.0.0, you need to use the older "upgrade.php" process.

gtomlin 2005-10-05 13:21 reporter ~0011468	Unfortunately, that's not what http://manual.mantisbt.org/manual.installation.upgrading.php says. Step 6 says: "6. Next we will update the necessary database tables. If you are upgrading from a pre-1.0.0 installation to 1.0.0, access http://yoursite/mantis-release/admin/upgrade.php. This will upgrade your database to 1.0.0. Once your database has reached release 1.0.0, you can use the method listed below. From your web server, access http://yoursite/mantis-release/admin/install.php" This suggests that a site that was at 1.0.0 should just run admin/install.php (I'm assuming that 1.0.0a2 counts as 1.0.0 here because it's not stated one way or the other).

thraxisp 2005-10-05 14:57 reporter ~0011469	I upgraded the manual source to read: If you are upgrading from a pre-1.0.0 (including 1.0.0a or 1.0.0rc) installation to 1.0.0, access http://yoursite/mantis-release/admin/upgrade.php. This will upgrade your database to 1.0.0. Once your database has reached release 1.0.0, you can use the method listed below. It should be public soon.

gtomlin 2005-10-07 10:30 reporter ~0011478	Thanks thraxisp. That clarifies who needs to run admin/upgrade.php.

anarchofascist 2005-10-30 23:47 reporter ~0011563	This still occurs on mantis-1.0.0rc3 I had no problems upgrading with admin/upgrade.php, but then when going back to the installation page this BAD CREATE TABLE error appears.

anarchofascist 2005-11-04 00:30 reporter ~0011591	.../admin/schema.php contains this line: $upgrade[] = Array('CreateTableSQL',Array(config_get('mantis_bug_file_table')," id I UNSIGNED NOTNULL PRIMARY AUTOINCREMENT, bug_id I UNSIGNED NOTNULL DEFAULT '0', ... I looked at our current schema and noticed that mantis_bug_file_table already exists and has content inside dating from 2003. Could this be the root of the problem? Does this table require modification and not creation during the upgrade?

anarchofascist 2005-11-04 00:45 reporter ~0011592	Liberally changing CreateTableSQL to ChangeTableSQL in admin/schema.php seems to have upgraded my tables to v1.0.0RC3 correctly.

grangeway 2007-07-16 14:58 reporter ~0015062	Marking this as resolved as it would seem you've manually managed to get your data upgraded. If your still having issues, can you let us know Paul