How to Resolve Diagnostic Collection with "bdadiag" Taking Excessive Time and Generating Files with Excessive Size in BDA V4.0 and Lower

Asset ID:	1-71-1934312.1
Update Date:	2017-07-15
Keywords:

Solution Type Technical Instruction Sure

Solution 1934312.1 : How to Resolve Diagnostic Collection with "bdadiag" Taking Excessive Time and Generating Files with Excessive Size in BDA V4.0 and Lower

Applies to:

Big Data Appliance X3-2 Hardware - Version All Versions and later
Big Data Appliance X4-2 Hardware - Version All Versions and later
x86 64 bit

Goal

Collecting a diagnostic bundle with "bdadiag" may take an excessive amount of time and generate an excessively large bundle on BDA V4.0 and lower versions. This is due to Bug 19655127 - ODI_GENERIC.JAR NOT REMOVED FROM TMP DIRECTORY IN SOME CASES.

This note documents a workaround for the issue. It may be especially useful when generating the Cloudera diagnostic bundle with "bdadiag cm" since information other than the Cloudera bundle is not necessary.

Solution

The workaround for bug 19655127 is to remove the odi_generic.jar files from "large" <cluster-name>-install-summary.zip files. The steps for doing so are below:

1. On Node 1 of the cluster from the '/opt/oracle' directory, find "large" <cluster_name>-install-summary.zip files. The example below uses a cluster name of 'bdax'.

a) Change directory to /opt/oracle

# cd /opt/oracle

b) Find the "large" files. In the output below './install/log/upgrade-20141008153316/summary/bdax-install-summary.zip' ~7GB is "large".

# find . -name <cluster-name>-install-summary.zip* -exec ls -l {} \;

Output like:

# find . -name bdax-install-summary.zip* -exec ls -l {} \;

-rw-r--r-- 1 root root 18635861 Oct 9 22:48 ./install/log/upgrade-20141008153316/summary/bdax-install-summary.zip
-rw-r--r-- 1 root root 6613011495 Oct 9 22:47 ./install/log/upgrade-20141008153316/summary/bdax4-install-summary.zip

2. Remove "odi_generic.jar" files from "large" <cluster_name>-install-summary.zip files.

# zip -d ./install/log/upgrade-20141008153316/summary/<cluster-name>-install-summary \*odi_generic.jar

Output like:

# zip -d ./install/log/upgrade-20141008153316/summary/bdax-install-summary \*odi_generic.jar

deleting: bdax-install-summary/log/install_logs/log/upgrade-20141008153316/tmp-bdaxnode02/odi_generic.jar
deleting: bdax-install-summary/log/install_logs/log/upgrade-20141008153316/tmp-bdaxnode03/odi_generic.jar
deleting: bdax-install-summary/log/install_logs/log/upgrade-20141008153316/tmp-bdaxnode04/odi_generic.jar
deleting: bdax-install-summary/log/install_logs/log/upgrade-20141008153316/tmp-bdaxnode05/odi_generic.jar
deleting: bdax-install-summary/log/install_logs/log/upgrade-20141008153316/tmp-bdaxnode06/odi_generic.jar
deleting: bdax-install-summary/log/install_logs/log/upgrade-20141008153316/tmp-bdaxnode01/odi_generic.jar

3. Confirm no more "big" files

# find . -name <cluster-name>-install-summary.zip* -exec ls -l {} \;

Output like:

# find . -name bdax-install-summary.zip* -exec ls -l {} \;

-rw-r--r-- 1 root root 18635861 Oct 9 23:39 ./install/log/upgrade-20141008153316/summary/bdax-install-summary.zip
-rw-r--r-- 1 root root 1354587 Oct 7 20:39 ./install/log/install-20141007201732/summary/bdax-install-summary.zip

4. Now collect the diagnostic bundle.

# bdadiag

For details on options to bdadiag like "bdadiag cm" see: Oracle Big Data Appliance Diagnostic Information Collection with bdadiag V2.*/V3.*/V4.* (Doc ID 1516469.1)

If you a Mammoth upgrade, install, or a "mammoth -c" cluster check generates a excessively large deployment summary see: How to Extract Required Files from an Extremely Large Deployment Summary Zipfile Generated by Mammoth in BDA V4.0 and Lower (Doc ID 1943192.1)

Attachments

This solution has no attachment