Mammoth Upgrade Fails On Step 2 with "ERROR: MySQL Slave IO Thread is not on: . Please fix it and restart operation."
Last updated on JANUARY 09, 2018
Applies to:Big Data Appliance Integrated Software - Version 4.7.0 to 4.9.0 [Release 4.7 to 4.9]
Running a Mammoth upgrade from V4.7.0 to V4.9.0 fails on Step 2 with:
SUCCESS: Executed verifyMySQLPasswd.sh on nodes /opt/oracle/BDAMammoth/bdaconfig/tmp/all_nodes #Step 2#
ERROR: MySQL Slave IO Thread is not on: . Please fix it and restart operation.
Verify from Node 1 as 'root' user unless specified otherwise.
1. The command "show slave status\G" hangs when logging into the MySQL secondary node, Node 2, from Node1 with the host option.
For example from Node 1 using the host (-h) option to log into the MySQL secondary node, hangs when running "show slave status \G" to check slave replication status.
6. The HCA firmware is found to be upgraded on Node 1 but not on any other node of the cluster.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms