i) Complete the installation, and then start the server. n Move the data directory from My SQL 5.0 to My SQL 5.1.
Optionally, you may also choose to restore the dump taken in step(a), however this is not feasible for production since the database is very large and would require a down time to restore. m) (Optional) Run the following to check incompatibilities between My SQL 5.0 - check the values set for the new columns.
This will ensure all our databases are moved now to Mysql 5.1. UPDATE SET character_set_client = ‘utf8’ , collation_connection = ‘utf8_general_ci’ , db_collation = ‘utf8_general_ci’ WHERE db_collation IS NULL; - update the values to utf8.
n In my.cnf, update the new location of base_dir and data_dir, socket information. p) My SQL Query Browser, My SQL Administrator, My SQL Migration Toolkit (My SQL GUI Tools) has reached its EOL.
The model can be downloaded from: We want to compute the Executes a sub-network of the network.
If you are using Flex servers follow [XCAT_system_x_support_for_IBM_Flex] or [XCAT_system_p_support_for_IBM_Flex] to set up the management node.Use My SQL Work Bench 5.2 instead, however one can still use older GUI tools.a) Take a dump of all your database along with procedures. c) Before upgrading My SQL, stop the server if running. Example: # rpm -qa | grep -i mysql mysql-libs-5.0.45-6.fc8 mysql-server-5.0.45-6.fc8 mysql-5.0.45-6.fc8 perl-DBD-My SQL-4.005-2.fc8.1 e) Remove all mysql packages related to 5.0: Example: #rpm –e mysql-libs-5.0.45-6.fc8 f) Download packages for Mysql 5.1 for Linux.x CAT depends on several packages that come from the Linux distro.Follow this section to create the repository of the OS on the Management Node.