My Oracle Support Banner

Mammoth Upgrade to 5.1 or Mammoth 5.1 Install Fails at "Bigdatasql::Manage_bds/Exec[install_bds]" with "No module named cryptography" (Doc ID 2642664.1)

Last updated on FEBRUARY 28, 2020

Applies to:

Oracle Big Data SQL - Version 3.0 and later
Big Data Appliance Integrated Software - Version 4.10.0 to 4.12.0 [Release 4.10]
Linux x86-64


NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, 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.

Mammoth upgrade to 5.1 or Mammoth 5.1 install fails at "Bigdatasql::Manage_bds/Exec[install_bds]" with "No module named cryptography".

The Mammoth failure looks like:

Error [3961]: (//<HOSTNAME3>.<DOMAIN>//Stage[main]/Bigdatasql::Manage_bds/Exec[install_bds]/returns)
change from notrun to 0 failed: /opt/oracle/BDAMammoth/bdaconfig/tmp/ &>
/opt/oracle/BDAMammoth/bdaconfig/tmp/install_bds_<EPOCH_TIMESTAMP>.out returned 1 instead of one of [0]

1. /opt/oracle/BDAMammoth/bdaconfig/tmp/install_bds_<EPOCH_TIMESTAMP>.out shows:

### pre-install BDS ###
Copying BDS bundle from mammoth node to CM node...
Unzipping bds bundle...
Running file...
Replacing oracle-hadoop-sql.jar file...
Copying bds config file...
Copying oracle.keytab and hdfs.keytab...
### install BDS ###
No module named cryptography. Please install the module, or upgrade Python to 2.7 or higher, and try again.
Error during the execution of the install workflow.

2. Checking the python2-cryptography rpm shows that it is not installed: 


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.