My Oracle Support Banner

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

Last updated on NOVEMBER 15, 2019

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


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:


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

Deployment Summary generated in /tmp/<cluster-name>
 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. 


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

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