Running bdachecksw Fails with Wrong" Package Errors after Oracle Big Data Appliance Upgrade (Doc ID 1677811.1)

Last updated on APRIL 22, 2016

Applies to:

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

Symptoms

After a BDA upgrade, the bdachecksw command fails with lots of  "Wrong" package errors.  In the example here after a BDA upgrade from version 2.0.1 to 2.3.1 errors like below are reported:

ERROR: Wrong Java Virtual Machine version : HotSpot(TM) 64-Bit Server 1.7.0_25
INFO: Expected Java Virtual Machine version : HotSpot(TM) 64-Bit Server 1.6.0_29 or HotSpot(TM) 64-Bit Server 1.6.0_37
SUCCESS: Correct puppet version : 2.6.11
WARNING: Wrong MySQL version : 5.5.33
INFO: Expected MySQL version : 5.5.17
SUCCESS: All required programs are accessible in $PATH
ERROR: Required package version jdk-1.7.0_25-fcs.x86_64 is not supported in release 2.3.1
ERROR: Required package version bash-3.2-32.el5.x86_64 is not supported in release 2.3.1
ERROR: Required package version coreutils-5.97-34.el5_8.1.x86_64 is not supported in release 2.3.1
ERROR: Required package version dnsmasq-2.45-1.1.el5_3.x86_64 is not supported in release 2.3.1
ERROR: Required package version expect-5.43.0-8.el5.x86_64 is not supported in release 2.3.1
ERROR: Required package version expect-5.43.0-8.el5.x86_64 is not supported in release 2.3.1
.......

 Note that the ERRORs are complaining about package versions that are in fact correct for the current BDA version e.g. BDA V2.3.1 in the example.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms