help --> Migration version 1.1.2 to 2.1.0

Get help from other users here.

Moderators: Developer, Contributor

Post Reply
totof044
Posts: 2
Joined: 13 Feb 2017, 10:07

help --> Migration version 1.1.2 to 2.1.0

Post by totof044 »

Hello all,

I must upgrade from mantis bug tracker version 1.1.2 to Mantis bug tracker version 2.1.0.
It s impossible to migrate directly. (database in latin1_swedish_ci , he wants UTF-8 collation and package database ?)
What is the best methodology?

example : I migrate from mantis version 1.1.2 to mantis version x.x.x.
and after i migrate from mantis version x.x.x. to Mantis bug tracker version 2.1.0. ?


mantis version 1.1.2 (original)
----------------------
- php version 4.64
- apache 2
- mysql version 5.54
- debian


mantis destination (test environnement)
------------------
- php version 5.5.38
- apache 2
- mysql version 5.0.11
- windows 7 (xamp installed)


I try to migrate from mantis version 1.1.2 to mantis 1.1.4. in the first time.
- install mantis version 1.1.4
- copy file custom_strings_inc.php; config_inc_php, etc..


http://localhost/mantis-1.1.4/admin/check.php
When I ckeck installation, the check are good.
but he displays
- Warning: ob_start(): function 'compress_handler' not found or invalid function name in C:\xampp\htdocs\mantis-1.1.4\core.php on line 39
- Notice: ob_start(): failed to create buffer in C:\xampp\htdocs\mantis-1.1.4\core.php on line 39

http://localhost/mantis-1.1.4/admin/install.php
when i click on button install/upgrade database,
-it follow the step new install not upgrade.
- it try to create the tables but the tables exist already. and the tables are not empty.

on the basic upgrade sets (required)
http://localhost/mantis-1.1.4/admin/upgrade.php
if i upgrade the package installation, i have the install errors ....
description upgrade id status
* Drop votes column of mantis_bug_table 0.17-jf-8 not applied
--> sql order : "ALTER TABLE $t_bug_table DROP COLUMN votes"
- unable because the colum doesn t exist in the table

* Add primary key on mantis_project_version_table 0.17-jf-9 not applied
--> sql order "ALTER IGNORE TABLE $t_project_version_table ADD PRIMARY KEY (project_id,version)"
the primary key exist already on key id (int 11) auto increment.
- unable to modifuy the primary key (no drop primary, and the colummn id is autoincrement ,this column must be in the primary key...

any idea How to do this migration ?

best regards
Christophe
atrol
Site Admin
Posts: 8366
Joined: 26 Mar 2008, 21:37
Location: Germany

Re: help --> Migration version 1.1.2 to 2.1.0

Post by atrol »

totof044 wrote: mantis destination (test environnement)
------------------
- php version 5.5.38
- apache 2
- mysql version 5.0.11
- windows 7 (xamp installed)
2.1.0 is not supported using the MySQL version, see http://www.mantisbt.org/docs/master/en- ... e.versions
Please use Search before posting and read the Manual
totof044
Posts: 2
Joined: 13 Feb 2017, 10:07

Re: help --> Migration version 1.1.2 to 2.1.0

Post by totof044 »

configuration
--------------
* apache 2.4.25 is installed
* database original 4 GB

- migration from mantis 1.1.2 to 1.2.0. --> ok
-----------------------------------------------------------------
* to do
-----------
INSERT INTO mantis_config_table ( value, type, access_reqd, config_id, project_id, user_id ) VALUES (63, 1, 90, 'database_version', 0,0 ) --> because the record is not pressent in the table.
copy file config
button install/upgrade

- migration from mantis 1.2.0 to 1.2.3. --> ok
-----------------------------------------------------------------
because i have the error htmlentities if update version > 1.2.3
copy file config
button install/upgrade

- migration from mantis 1.2.3 to 1.2.19 --> ok
-----------------------------------------------------------------
copy file config
button install/upgrade

- test to migration from 1.2.3 or 1.2.19 to 1.3.x -- crash
--------------------------------------------------------------

--> tables are not in utf8_general_ci but in utf8_swedish
--> error Schema step 193: UpdateFunction ( check_config_serialization ) - BAD

* i do
---------
--> conversion utf8_general_ci;

- ALTER TABLE <name_table> CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci;
<name_table> ---> bugtracker.mantis_bug_file_table, bugtracker.mantis_...

example : ALTER TABLE bugtracker.mantis_bug_file_table CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci;

---> all tables are not convert in utf8_general_ci after this command ?
12 tables on 30 not convert in ut8_general_ci
the tables are not empty.
some tables haven't the columns characters or text... but column integer...
some tables have colum text or longtext and integer but not convert in ut8_general_ci ?

----------------------------
any idea to migrate to mantis 2.1 and convert table utf8_general_ci...
Post Reply