My Oracle Support Banner

bdacheckcluster/bdacheckhw on BDA 4.12 and Lower Raises "" WARNINGS on New X7-2 Servers (Doc ID 2478259.1)

Last updated on FEBRUARY 10, 2021

Applies to:

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


NOTE: In the examples that follow, user details, table name, company name, email, hostnames, 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.

The bdacheckcluster utility on BDA V4.12 and lower raises "" WARNINGS on new X7-2 servers.  The error is reported by bdacheckhw, but it can cause bdachecksw/bdacheckcluster to hang.

This may be seen after a BDA Mammoth cluster expansion when running bdacheckcluster manually or as part of the Mammoth cluster verification step.  The symptom will be that bdacheckcluster raises "" WARNINGS on all new X7-2 servers.

After a BDA Mammoth expansion, if bdacheckcluster hangs when the "" faults are raised, make sure to review the first step in the "Post Expansion Steps" section of: Expanding an Oracle Big Data Appliance V4.5 and Higher Cluster (Doc ID 2478298.1).  It is critical to verify that /opt/oracle/bda/install/state/config.json does not contain more that one occurrence of the same hostname or IP address in each of the file's "RACKS" sub-arrays.  This can contribute to the faults being generated and bdacheckcluster hanging.

bdacheckcluster output looks like below: 

See the next sections for a discussion on the relevant faults and how to clear them.


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
 Detailed Steps
 Appendix A

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