How to Extract Required Files from an Extremely Large Deployment Summary Zip File Generated by Mammoth in BDA V4.0 and Lower

Asset ID:	1-71-1943192.1
Update Date:	2014-11-11
Keywords:

Solution Type Technical Instruction Sure

Solution 1943192.1 : How to Extract Required Files from an Extremely Large Deployment Summary Zip File Generated by Mammoth in BDA V4.0 and Lower

Applies to:

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

Goal

During a Mammoth software upgrade, install, or when running the "mammoth -c" option to run the Oracle Big Data Appliance cluster checks an excessively large deployment summary zip file may be created. Sizes can be in the range of 7, 13, 65 Gigabytes. The deployment summary zip will be placed into:

/tmp/<clustername>-install-summary.zip

Mammoth will generate a line indicating the name and location of the file which looks like:

Deployment Summary generated in /tmp/<cluster-name>-install-summary.zip
Copy this to the usb drive for printing

The size of the file may make it difficult to upload.

One factor contributing to an excessively large bundle is: Bug 19655127 - ODI_GENERIC.JAR NOT REMOVED FROM TMP DIRECTORY IN SOME CASES.

Solution

A workaround in the case of an extremely large generated deployment summary file is to extract out the required files into a new deployment summary file. The new deployment summary zip file will be /tmp/deployment-summary.zip.

Follow these steps on Node 1 of the cluster as 'root' user. The example here uses a cluster-name of "bdax".

1. Create a variable with the cluster name.

# export clustername=<cluster-name>

For example:

# export clustername=bdax

2. Change directory to /tmp.

# cd /tmp

3. Remove the existing deployment summary directory

# rm -rf /tmp/$clustername-install-summary

4. Create a new deployment summary directory containing the summary html and jpg file.

# unzip /tmp/$clustername-install-summary.zip $clustername-install-summary/summary.html $clustername-install-summary/im08t0-big-data-appliance-1-1455686.jpg

Output is like:

Archive: /tmp/bdax-install-summary.zip
inflating: bdax-install-summary/summary.html
inflating: bdax-install-summary/im08t0-big-data-appliance-1-1455686.jpg

5. Create a new deployment summary with the name deployment-summary.zip

# zip -r deployment-summary.zip $clustername-install-summary

Output is like:

adding: bdax-install-summary/ (stored 0%)
adding: bdax-install-summary/summary.html (deflated 77%)
adding: bdax-install-summary/im08t0-big-data-appliance-1-1455686.jpg (deflated 7%)

If having a similar issue with bdadiag taking excessive time and generating files with excessive size see: How to Resolve Diagnostic Collection with "bdadiag" Taking Excessive Time and Generating Files with Excessive Size in BDA V4.0 and Lower (Doc ID 1934312.1)

References

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

Attachments

This solution has no attachment