My Oracle Support Banner

Mammoth Upgrade Fails On Step 2 with "ERROR: MySQL Slave IO Thread is not on: . Please fix it and restart operation." (Doc ID 2346516.1)

Last updated on JANUARY 22, 2020

Applies to:

Big Data Appliance Integrated Software - Version 4.7.0 to 4.9.0 [Release 4.7 to 4.9]
Linux x86-64


NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner. 

Running a Mammoth upgrade from V4.7.0 to V4.9.0 fails on Step 2 with:

SUCCESS: Executed 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.

Additional Symptoms:

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.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.