Running asrexachk on BDA V3.*/V4.* Raises, "/opt/oracle/bda/install/state/mammoth-saved.params: No such file or directory"

Asset ID:	1-72-1956738.1
Update Date:	2014-12-23
Keywords:

Solution Type Problem Resolution Sure

Solution 1956738.1 : Running asrexachk on BDA V3.*/V4.* Raises, "/opt/oracle/bda/install/state/mammoth-saved.params: No such file or directory"

Applies to:

Big Data Appliance X4-2 Hardware - Version All Versions and later
Big Data Appliance Integrated Software - Version 3.0.1 and later
x86_64

Symptoms

From Node 1 of a cluster as 'root' running 'asrxachk' raises syntax related errors on BDA V3.*/V4.* as below.

# cd /opt/oracle.SupportTools
# ./asrexachk

grep: /opt/oracle/bda/install/state/mammoth-saved.params: No such file or directory

Cause

BUG 20229882 - ASRExachk/BDA is not working since a path changed in installation on the BDA

Solution

Until BUG 20229882 is resolved you can manually edit /opt/oracle.SupportTools/asrexachk. An overview of the steps follows. An example of the changes done on BDA V3.1 is below:

1. Backup /opt/oracle.SupportTools/asrexachk to a safe location, and make a copy on Node 1 of the cluster.

2. Update the copy of /opt/oracle.SupportTools/asrexachk.

a) The script is checking /opt/oracle/bda/install/state/mammoth-saved.params:
INSTALL_INFO="/opt/oracle/bda/install/state/mammoth-saved.params"

"/opt/oracle/bda/install/state/mammoth-saved.params" no longer exists in BDA V3/V4. One workaround is to use a conditional to workaround this check.
For example instead of: INSTALL_INFO="/opt/oracle/bda/install/state/mammoth-saved.params", try something like:

if [ -f /opt/oracle/bda/install/state/config.json ]; then
INSTALL_INFO="/opt/oracle/bda/install/state/config.json"
else
INSTALL_INFO="/opt/oracle/bda/install/state/mammoth-saved.params"
fi

b) The test around Line 1486 is also based on the /opt/oracle/bda/install/state/mammoth-saved.params file. The line looks like:
ASR_ENB=`grep -i "ASR_ENABLED" $INSTALL_INFO | /usr/bin/awk -F= '{ print $2 }'`

However in BDA V3.*/V4.* /opt/oracle/bda/install/state/config.json uses a syntax of:
"ASR_ENABLED" : "true",

The syntax in /opt/oracle/bda/install/state/config.json needs to be parsed differently. For example use something like:

ASR_ENB=`grep -i "ASR_ENABLED" $INSTALL_INFO | /usr/bin/awk -F: '{ print $2 }'`
ASR_ENB=${ASR_ENB:2:4}
if [ "$ASR_ENB" == "true" ]; then

These changes should allow /opt/oracle.SupportTools/asrexachk to execute successfully.

References

<BUG:20229882> - ASREXACHK/BDA IS NOT WORKING SINCE A PATH CHANGED IN INSTALLTION ON THE BDA

Attachments

This solution has no attachment