Problems with mysql migration to db2

I have never encountered any problems with migrating mysql to db2 before, so this work has been very hard. The following problems occur: installation problem www.2cto.com 1. for user problems, users with different permissions must be created and different users must do different things. 2. db2 Installation File problems, db2 has various versions, various patches 3. for installation problems, the installation must be in a specific environment, such as the C environment of the system. The version of the installation package is different. 4. the user password is incorrect. in linux, sha512 is used for encryption by default. You need to change the password to md5. Otherwise, the connection fails. port problem. It is not successful to set the port with commands, and the default port is not necessarily 50000. the db2 port is set.
Not necessarily the current database port 6. for user problems, mysql must use users with DBA permissions, while db2 must use instances to manage users. for permission issues, it is best to place the tool under the user permission of the db2 instance 8. db2 database usage problems. Db2 instances, modes, databases, and permissions are not clearly identified. 9. db2 case sensitivity issues. 10. The conversion tool is IBMDataMovementTool. There are many parameters to configure for this tool.
If an error occurs, www.2cto.com or below is a problem caused by a problem with the mysql database. You need to modify the mysql DATA first. You can view the log to find 1. if the unique index field is null, db2 deletes the data when checking the data rationality. if the db2 version is incorrect, the foreign key name cannot be too long. Otherwise, table creation fails. 3. if the db2 version is incorrect, clob cannot be too large. Otherwise, table creation fails. 4. the table is not activated due to garbled characters. the length of the mysql field is different from that of the db2 field, resulting in data insertion being truncated. the primary key name is too long. As a result, the primary key cannot be created successfully. set the initial default value. If it is boolean, an error 8 is returned. the engine used to modify the data table is MyISAM. If a problem exists, the following foreign keys are not supported: Problem 1. group by problem, hibernate related