CUBRID Migration Toolkit Release Notes

Release Note Summary

CUBRID Migration Toolkit 8.4.1.201204 Hot fix build 2004 (2012-04-16)

Supported CUBRID version

• CUBRID 8.2.2.x ~ CUBRID 8.4.1.2032

Improvement

• TOOLS-919 - Remove duplicated index names checking at the stage 4 of migration wizard

Bug

• TOOLS-886 - Migrating large online mysql database may rise out of memory errors

CUBRID Migration Toolkit 8.4.1.201203

Supported CUBRID version

• CUBRID 8.2.2.x ~ CUBRID 8.4.1.0558

New Feature

• TOOLS-512 - Auto update support (using eclipse p2)
• TOOLS-807 - Add the update url to install new software

Improvement

• TOOLS-622 - Typo in english messages
• TOOLS-626 - Commit unit : 500 is too low for new version tools and engine. Let's find optimized value.
• TOOLS-691 - When create new JDBC connection in step 2 of migration wizard, the default database type is CUBRID and the driver is the newest version.
• TOOLS-707 - Improve the performance of FTP
• TOOLS-723 - The database type have to be selected CUBRID Database in New Database connection dialog of Migration Wizard Step 2
• TOOLS-740 - Modify name of Wizard Step two
• TOOLS-760 - Cannot migrate number partition table to CUBRID via CMT
• TOOLS-782 - Cannot support migrate sub partition from oracle to cubrid.

Bug

• TOOLS-346 - Modify cms user, the database display error
• TOOLS-360 - When the index name are same in two tables,goto step4, the index's table is error
• TOOLS-361 - When do offline migration, the directory of loaddb log is error.
• TOOLS-412 - From xml to CUBRID, bit data type convert is error.
• TOOLS-472 - Do migration view, there is different in migrate to online db and file.
• TOOLS-498 - In step2, change online db to EUC-KR, save XE. Then change the online db's charset to UTF-8. Use the XE, charset cannot be modified.
• TOOLS-500 - the data is inconsistent after migrating binary type to bit type(or varbinary type to bit varying type)
• TOOLS-501 - the data is inconsistent after migrating binary type to character type(xml migration)
• TOOLS-505 - In step5, please change dafult timezone to actual data
• TOOLS-519 - The order of columns of tables having more than one columns is wrong(it is opposite) after convering DB with offline form.
• TOOLS-543 - When there is one table has double quotation marks, cannot do migration.
• TOOLS-572 - When migrated some data type to nvarchar, please add the confirm info.
• TOOLS-599 - Migrate to windows server, it will be error
• TOOLS-602 - When there are same name in select statements, the target column name will be lost
• TOOLS-604 - In DB Records of migration report, the align of - is not same.
• TOOLS-610 - When start oracle after login CMT, connect oracle server in step1, it cannot connect.
• TOOLS-621 - Does not like to port some tables from database - keyword problem?
• TOOLS-731 - When there are two table name is same, there are two warning.
• TOOLS-741 - When migrate the partition table, it has been migrated, but there display error in migration report.
• TOOLS-745 - When migrate the table which name has "", the table can be migrated successfully, but the data has been lost
• TOOLS-749 - When connect to mysql database, cannot connect the database in upper case
• TOOLS-750 - There isn't distinguish upper case and lower case in step3.
• TOOLS-754 - Creating new database can be canceled.
• TOOLS-755 - When do offline migration to create new database via CMT, the process blocked.
• TOOLS-758 - When load the txt which are migrated from mysql to file, some object cannot be loaded.
• TOOLS-761 - Do migration from numer to varchar, it will pop warning
• TOOLS-762 - When do migration from xml to offline cubrid, It will lost partition
• TOOLS-763 - When migrate two table which have same name, click back,delete one table, the duplicate judgement still exist.
• TOOLS-767 - When there are two table name is same and one has fk, it will be pop error in migration process.
• TOOLS-770 - When add two connection in step1, one is upper case, the other is lower case,it will display one.
• TOOLS-784 - When migrate partition to CUBRID, please add " " on the partition filed
• TOOLS-785 - When the server is run in standalone mode, there will be pop user and password incorrect.
• TOOLS-786 - There doesn't display the referenced table name in step 4.
• TOOLS-788 - When there are two index in one table, change to same index name in migration,it will be error
• TOOLS-789 - When there are two table name is same and one has fk, the referenced table will be lost in step4
• TOOLS-792 - When copy one url to install other software UI, it will pop error.
• TOOLS-798 - When migrate from oracle, there is untidy of tables.
• TOOLS-800 - When migrate from XE template, the partition ddl will be lost in step4
• TOOLS-801 - Do migration from oracle, when there are two tables which name is same. The data migration is error.
• TOOLS-802 - When do migration from oracle to cubrid, it will pop error.
• TOOLS-803 - When create new database via cmt use the other user, it cannot be login with dba.
• TOOLS-806 - Check for update doesn't work
• TOOLS-812 - When do migration use XE(migrate to file), cannot migrate.
• TOOLS-816 - There will be pop error in migration, but it doesn't display every time.
• TOOLS-825 - Don't choose XE serial in XE ui, but it migrate the xe serial in migration
• TOOLS-829 - When generate XE to change file name in database unload UI. The file name isn't saved.

Task

• TOOLS-460 - Migrate partition table in mysql to database, the partition will be lost
• TOOLS-513 - The parser of MYSQL XML dump file can read the invalid XML characters correctly
• TOOLS-747 - Migrate source code from svn.platform.nhncorp.cn to dev.nave.com
• TOOLS-394 - the object for checking new version is wrong(it is for cubrid in this version, not for cubridmigration)
• TOOLS-532 - Change cubridmigration.exe icon to new icon.
• TOOLS-603 - The char ' ' in the XML dump file will be lost during migration

CUBRID Migration Toolkit 8.4.1

Supported CUBRID version

• CUBRID 8.2.2.x ~ CUBRID 8.4.1.0558

Improvement

• TOOLS-95 - human readable/editable template file
• TOOLS-96 - increase performance of MySQL dump file parsing
• TOOLS-121 - support cancel migration task even which run on server side as standalone process
• TOOLS-228 - CM server improvements
• TOOLS-337 - There is error in migration, the migration progress bar isn't finished
• TOOLS-355 - Please add one summary which is like step5 to migration history
• TOOLS-358 - Goto step4, don't choose create new table and data migration for one table, goto report, the table will display error, please add some error infor
• TOOLS-490 - Add charset in file repository.

Task

• TOOLS-110 - Improve migration working engine
• TOOLS-111 - Data transform engine
• TOOLS-112 - Improve migration wizard UI
• TOOLS-569 - To support CUBRID 8.4.1 and prepare release build
• TOOLS-600 - It is needed a brandnew version string that it easily support for CUBRID compatibility.

Bug

• TOOLS-306 - In step2, click off line, database should display offline database. But there is all database.
• TOOLS-309 - After migration, the process bar isn't finished
• TOOLS-310 - Offline migration to online database, it can do migration.
• TOOLS-314 - In step2, connect one online server, then stop the server, do migration, the result is error
• TOOLS-321 - XML to cubrid, datetime data type transfer error
• TOOLS-322 - When there are two index which has same name in xml, one index will be error.
• TOOLS-324 - XE template saved can't reproduce former step(that is step 2:select target database) when using the converting form: online->file repository.
• TOOLS-341 - Migrate to file repository, the file hasn't override the target files
• TOOLS-345 - After do offline migration, the target database hasn't data.
• TOOLS-351 - Migrated FK from Mysql to CUBRID, if one table has primary key, the FK will became index
• TOOLS-353 - When multitype in tables, the view hasn't multitype.
• TOOLS-354 - Export migration report to excel. The sheet is ambiguous.
• TOOLS-356 - The progress bar is not complete when converting database.
• TOOLS-359 - the index of type "unique" can not be converted to type of "reverse unique" or "reverse index"
• TOOLS-362 - Multiplication should be decided by the charset target database.
• TOOLS-363 - Changed charset in step1, the index, PK migrated failed
• TOOLS-368 - There is no effect for step 4 when be back to step 3 from step 4 to edit the "select statement" table name.
• TOOLS-369 - There is no effect for "ok" button when selecting other charset from default.
• TOOLS-371 - In step4,choose don't create table, goto migration report, display migrate table error.
• TOOLS-377 - Bit(1) cannot migrate to target database.
• TOOLS-378 - The time form in log is inconsistent.
• TOOLS-379 - Only choose some fields to do migration, the cut is error
• TOOLS-385 - After migration, binary(255) cannot be migrated
• TOOLS-386 - After convert blob to bit, the target data is error.
• TOOLS-388 - bool and boolean convert is error
• TOOLS-389 - the index of type "unique" can not be converted to type of "reverse unique" or "reverse index"(mysql->offline db)
• TOOLS-391 - In date data type migration, it will be error
• TOOLS-392 - The form of time is 12h(I think it should be 24h) and the statement should not be ended ";".
• TOOLS-393 - the hint in the status bar of help system is wrong.
• TOOLS-397 - Migrated from online db view to file, the report and the file contents isn't consistent.
• TOOLS-400 - Migrated decimal to numeric, it will be error in migration.
• TOOLS-401 - When migrating from db to online database, stop db server. In migration
• TOOLS-404 - Enum type can't migrated to target type successfully when changing target column name
• TOOLS-405 - Longtext type can't be migrated to target type successfully when changing the target column name.
• TOOLS-406 - Migrated float , it will be error.
• TOOLS-410 - Save XE to one exist xml, it will pop failed.
• TOOLS-413 - In migration from xml to file, datatime is error.
• TOOLS-414 - Migrated from online db to cubrid, datetime convert is error.
• TOOLS-415 - In sometime, the log will be combined.
• TOOLS-419 - When migrate varbinary(65532) to bit varying, the big value cannot be migrated.
• TOOLS-420 - When migrate the data type about int error, the report error.
• TOOLS-422 - The function of "Data Migration" has no effect
• TOOLS-425 - When do xml to cubrid migration, if change the source charset, it will migrate error.
• TOOLS-428 - In report,click the canceled DB Objects, it hasn't display name.
• TOOLS-429 - The view ddl in the file migrated display is not good
• TOOLS-432 - there is an error when migrating a table of year type.
• TOOLS-437 - When multiplicated in tables, the view hasn't been multiplicated.
• TOOLS-440 - Choose the replace table in step3, haven't delete index.
• TOOLS-441 - Migrated the table which has two fk will error
• TOOLS-443 - In step4, can change view sql, but when migrate, it will be error
• TOOLS-445 - the prompt of "Save current tab to file" is not exact and should be like another prompt "Save all tabs to an excel file"
• TOOLS-448 - When choose something, it will pop nullpointerException.
• TOOLS-451 - the parameter of "NULL" about time in migration parameters of Preferences has no effect
• TOOLS-452 - the parameter of "Replace with" about time in migration parameters of Preferences has no effect
• TOOLS-453 - the parameter of "NULL" about date in migration parameters of Preferences has no effect
• TOOLS-455 - the parameter of "Replace with" about date in migration parameters of Preferences has no effect
• TOOLS-456 - the parameter of "NULL" about timestamp in migration parameters of Preferences has no effect
• TOOLS-457 - the parameter of "Replace with" about timestamp in migration parameters of Preferences has no effect
• TOOLS-459 - The default XE template cannot be used
• TOOLS-462 - the table of type converting can be edit to anything(please do some limit when editing them)
• TOOLS-463 - Migrated datetime from xml and online database, it's different.
• TOOLS-466 - Migrate xml charset is not utf8, it will be error.
• TOOLS-467 - the "0"(zero) in the data(the "0" is in the end) will be lost when converting binary to bit.
• TOOLS-469 - there is an error when two user migrate two different databases to the same target database concurrently
• TOOLS-470 - In the new version, do migration from online db to new db, many tables cannot be migrated
• TOOLS-471 - the negative number and zero will be converted to "0" and positive number will be converted to "1" when converting bool type to smallint type.
• TOOLS-473 - the data is inconsistent when migrating date type to date type
• TOOLS-474 - Migrate xml to online cubrid, bit data is error
• TOOLS-475 - Migrate bit(1) from xml to online database, it doesn't work
• TOOLS-476 - Migrate numeric to numeric,some data hasn't been migrated
• TOOLS-477 - Do migration from loaddb, the blob content directory cannot found.
• TOOLS-478 - the data is inconsistent when migrating datetime type to datetime type
• TOOLS-479 - Migrated from xml to new DB and from mysql DB to new DB,the data of bool data type isn't same.
• TOOLS-480 - the data is inconsistent when migrating double type to double type
• TOOLS-481 - the window of "preferences" can not be closed when you click "close" icon first time under certain conditions.
• TOOLS-482 - Migrated from xml to offline db, timezone from default to default, timestamp is error
• TOOLS-483 - the data is inconsistent when migrating double unsigned type to double unsigned type
• TOOLS-484 - Migrate xml to online cubrid, datetime,time,timestamp data is error
• TOOLS-485 - the data is inconsistent when migrating float type to double type
• TOOLS-486 - the data is inconsistent when migrating float unsigned type to double type
• TOOLS-487 - the migration of converting longblob type to blob type is failed
• TOOLS-489 - the data is not what we expects it to be when migrating numeric(20,10) type to numeric(20,8) type
• TOOLS-491 - In step2, choose timezone in file repository. Save XE,
• TOOLS-493 - Choose all in step3, save XE, the sequences cannot been saved
• TOOLS-494 - the data is inconsistent when migrating year type to character type
• TOOLS-496 - By some way, XE cannot be used.
• TOOLS-503 - Use XE which is export mysql DB to online DB, delete online DB, it will pop "Failed to connect database server"
• TOOLS-504 - Migrate online to file ,it will pop java.lang.NullPointerException
• TOOLS-506 - When delete migration history, please give confirm info.
• TOOLS-507 - Use XE, "add prefix to index names" doesn't work
• TOOLS-508 - After some operation, it will pop NullPointerException
• TOOLS-509 - the parameter of "Replace with" about time in migration parameters of Preferences has wrong effect
• TOOLS-515 - There is some error about display in ubuntu 64 bit or windows
• TOOLS-517 - There is an error after migrating a big xml(but having no error after migrating the same xml)
• TOOLS-523 - The index name of target DB is not the same with the name in the field of "Target Index Name"
• TOOLS-524 - The function of "Replace Existed Tables" has some errors when replacing table which have FKs(you must notice the order of deleting these tables)
• TOOLS-527 - After extract the new version, login cmt, in the copyright of CUBRID Migration Toolkit, there are Chinese word.
• TOOLS-529 - Migrate blob data type to file, it record the absolute path
• TOOLS-533 - Migrate big xml (test.xml) to file, will have some index will be canceled.
• TOOLS-534 - When do migration from big xml to offline, sometimes pop "listen:Address already in use <end> "
• TOOLS-539 - Migrate bfile data type, the default glo is not defined
• TOOLS-540 - When get data from source database, the waring word in Chinese is error
• TOOLS-541 - When there are composite primary key, it will be error.
• TOOLS-542 - Migrated from oracle to cubrid, there is clob data type, it cannot migrated.
• TOOLS-544 - Migrate from oracle to cubrid, the migration from timestamp withe local time zone and time stamp with time zone to datetime is error
• TOOLS-545 - Migrated from bfile to blob, it hasn't been migrated
• TOOLS-546 - Migrate from blob to blob,clob to clob, nclob to nclob the data hasn't been migrated
• TOOLS-548 - The data of the two type "INTERVAL YEAR TO MONTH" and "INT,INTERVAL DAY TO SECOND" will be converted to "NULL" when using the converting form Oracle DB->online
• TOOLS-549 - The record of long type cannot be converted(oracle db->online)
• TOOLS-550 - Migrate from date date type to date, it will lost time.
• TOOLS-551 - Migrated date 0000-0-0 to date, it became 4713-01-01
• TOOLS-553 - Migrate from urowid to varchar, the value is error
• TOOLS-554 - Migrate long raw to bit varying(1073741823), it isn't same as raw to bit varying
• TOOLS-556 - Migrate int to int, some data cannot be migrated.
• TOOLS-558 - The record of number type cannot be converted(oracle db->online)
• TOOLS-561 - The data migration from decimal, number to number is different in migration from oracle and mysql
• TOOLS-563 - Migrate from interval_day_to_second to varchar, the data is not good
• TOOLS-564 - Migrate interval to Varchar, the data type is constant , but it times 3.
• TOOLS-565 - Migrate from real to float, the data cannot be migrated
• TOOLS-566 - Migrate int to numeric(38,0), the data cannot be migrated.
• TOOLS-568 - Migrate from date to datetime, the data is error
• TOOLS-577 - In migration, there is pk and unique index, the unique constraint will be lost.
• TOOLS-578 - Migrate FK on delete no action from oracle to cubrid, the action change from no action to restrict.
• TOOLS-581 - Normal index cannot be migrated from oracle to cubrid.
• TOOLS-583 - When there are procedure, trigger, function in oracle db, migrate from oracle to cubrid, the nonsupport objects is error
• TOOLS-585 - SQL statement hasn't multiply.
• TOOLS-586 - There is a help mark(?) in the interface of "Preferences"
• TOOLS-587 - There is an extra word in the sentence "To File Repository Commit Count"
• TOOLS-589 - Migrate date data type to offline db, datetime changed too.
• TOOLS-590 - Oracle has change timezone to GMT+04:00, but in step5 in migration, it display GMT+08:00
• TOOLS-591 - When do big xml migration, there are wait long time sometimes.
• TOOLS-592 - There is a wrong word in "Preferences"
• TOOLS-595 - In xe, the index hasn't be saved.
• TOOLS-597 - The primary key can not be created when migrating mysql db to offline db..
• TOOLS-598 - When do migration use XE, the sequence will be error

CUBRID Migration Toolkit 1.5.5

Bug

• TOOLS-165 - Display referential ations on "FK" and apply that option a user chooses to tables by asking "you want to apply the option to all tables?"
• TOOLS-212 - Migrate partition table to CUBRID8.4.0 successfully. But the table is migrated to CUBRID8.4.1 is error.
• TOOLS-229 - Use XE to do migration, go to step5 , then back to step1, omit XE, goto step3, only display the table which in XE
• TOOLS-255 - The csql error is occurred when click the Check Owner with no-inputted User name and Password form on the migration wizard step 4
• TOOLS-267 - When using "Load Migration Script" menu, target table name is always empty in the SQL tab in the step 5.
• TOOLS-268 - In step4, after choose "Skip Check of the exist database name and the owner name", then choose Create new database, the warning is error
• TOOLS-273 - After migrate the source database to txt file, the import record count of migration statistic report display exported
• TOOLS-274 - Migrate decimal data type to CUBRID, the target data type is error
• TOOLS-282 - From mysql to CUBRID, the FK migration is not right.
• TOOLS-286 - Migrated FK from Mysql to CUBRID, if one table has primary key, the FK will became index
• TOOLS-291 - When we choose the XE, click next. It cannot goto step 2
• TOOLS-292 - The same xml migrated to old version and new version, the result is not same.
• TOOLS-293 - Use XE, do migration, goto step 6, the UI is error. The result of step 7 is error too.
• TOOLS-296 - It occur a error sometimes when using customized XE template because it didn't create new database.
• TOOLS-297 - After add the attention of alert of the no logging option using, has error.
• TOOLS-298 - In some times, the import record count will display error
• TOOLS-299 - Use XE, migrated xml, if the xml has fk, the fk become to index, and the index hasn't been choosed.

Improvement

• TOOLS-166 - In the wizard 1, it should nitoce the user that CMT server should be installed in the CUBRID server
• TOOLS-253 - A default values of a database volumn auto extends option is not same of CMT and CM (CMT와 CM 에서의 데이터베이스 생성시의 Default화면이 다릅니다)
• TOOLS-264 - Improve a multibyte charset supports.
• TOOLS-265 - Users difficult to know whether change to resize when a database has multi-bytes character set.
• TOOLS-266 - For users convenience, some of the menu needs to be put on the toolbar.
• TOOLS-295 - Need to show a alert dialog when using a --no-logging option in the migration step 6.
• TOOLS-288 - Include a recent driver of CUBRID 8.4.0 in CMT 1.5.5

New Feature

• TOOLS-262 - Can create the loaddb type data files without a database import
• TOOLS-263 - Add to select a table method with a file of a table name list in wizard step 3

CUBRID Migration Toolkit 1.5.4

Bug

• TOOLS-143 - In migration history, cannot choose any record, click delete button. It will prompt "Are you sure to delete the migration history"
• TOOLS-144 - When new database connection, the JDBC driver hasn't display order by version desc
• TOOLS-145 - In step1, when choose use default XE, click next. It will pop a process windows, but the cancel button is disable.
• TOOLS-148 - Input a not available remote migration server ip , It can go next from step 1 to step 2 when you use an available IP to test connection before
• TOOLS-163 - When loading table schem with default values, it quotes the values of some (randomly)
• TOOLS-164 - CMT automatically increases the size to2X or 3X depending on CHARSET to handle the multi-byte characters.
• TOOLS-167 - In migration, if import data is less than export, there isn't warning.
• TOOLS-169 - CMT returns no error when checking the option "creating a new database" on the wizard 4 in the localhost without installing cubrid server
• TOOLS-170 - When SELECT statement are entered to extract part of records only from the source DB, CMT doesn't work well.
• TOOLS-189 - JDBC 드라이버 오류로 인한 오라클 삭제된 테이블 조회되는 오류
• TOOLS-190 - In step1, input error ip, it will pop null
• TOOLS-196 - Slowly sub-query issue while checking SQLs syntax
• TOOLS-210 - When SELECT statement are entered to extract part of records only from the source DB, CMT doesn't work well.
• TOOLS-216 - In migration report wizard,the load a xml file time error
• TOOLS-222 - change the checkbox(change all the solumn size of char .....)in the migration wizard step 2,the step 5 page's content don't update.
• TOOLS-223 - Do migration by XE template, migrate xml file, it will pop error sometimes.
• TOOLS-226 - In windows64, there is a charset of cp1252 in step 4
• TOOLS-227 - Use XE to create XE, found the table will be lost

Improvement

• TOOLS-24 - CMT 용어 개선 및 설명
• TOOLS-102 - CMT supports Mac OS

New Feature

• TOOLS-23 - CMT 인댁스 수 Before/after 비교하기

CUBRID Migration Toolkit 1.5.3

Improvements and bug fixes

• TOOLS-76 - CMT report improved
• TOOLS-96 - There is a big improvement of parsing MySQL dump file .
• TOOLS-97 - If data source is xml file, the condition input cell will be read-only.

CUBRID Migration Toolkit 1.5.0

• CUBRID Migration Toolkit 1.5.0 Release Note_en.pdf