Last updated on APRIL 01, 2017
Applies to:Big Data Appliance Integrated Software - Version 4.5.0 and later
To resolve the case where the following has occurred on the BDA:
1. The MySQL master has stopped generating binary log files and consequently the MySQL slave does not have replication turned on. This could happen if /var/lib is full preventing data from flushing to disk, leaving some new data stored in memory.
2. The MySQL slave does not have replication turned on and due to the size of the databases taking downtime and copying the files is preferred to the steps in the "Verify the MySQL master/slave hosts" section in How to Reset MySQL Slave Replication without Full BDA Cluster Downtime (Doc ID 2152683.1).
Note: The steps here can also be considered an alternative process to use if you need to restore a slave to rebuild the master. Both MySQL master and slave need to be stopped and the cluster needs to be shutdown as per the note. The MySQL slave's data can be copied to the MySQL master, basically the same process but in reverse.
The steps in the example were done on MySQL 5.6. But they apply to MySQL 5.5 with the differences pointed out below.
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