My Oracle Support Banner

Upgrade From 4.5.0 To 4.8.0 Fails At Step 6 fails with "Mysql::Upgrademysql/Exec[mysql-upgrade]" (Doc ID 2305902.1)

Last updated on JANUARY 15, 2020

Applies to:

Big Data Appliance Integrated Software - Version 4.5.0 and later
Linux x86-64

Symptoms

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. 

Upgrade to 4.8.0 fails at Step 6 with:

ERROR: Puppet agent run on node bdanode02 had errors. List of errors follows

************************************
Error [9179]: (//bdanode02.example.com//Stage[main]/Mysql::Upgrademysql/Exec[mysql-upgrade]/returns) change from notrun to 0 failed: /usr/bin/mysql_upgrade -uroot -p'<password'' --force returned 4 instead of one of [0]
************************************

INFO: Also check the log file in /opt/oracle/BDAMammoth/bdaconfig/tmp/pagent-bdaxnode02-20170909031747.log


Additional Symptoms are:

1. The upgrade is  stuck because the Cloudera Manager(CM) server,  cloudera-scm-server which will not stay up.  On the node with CM server role, Node 3 by default see:

 

Cause

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
Symptoms
Cause
Solution


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