My Oracle Support Banner

Final Cluster Verifications Fail on Step 12 of a BDA 4.12 Mammoth Install with "Permission denied: user=oracle, access=EXECUTE, inode="/tmp":hdfs:supergroup:d-w" (Doc ID 2424367.1)

Last updated on MAY 17, 2021

Applies to:

Big Data Appliance Integrated Software - Version 4.12.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. 

The final step of the BDA V4.12 install may show most cluster verification tests failing like below:

BDA_Cluster_Check bdacheckcluster.out    SUCCESS      139
Teragen-sort-validate_Test terasort.out    ERROR           22
Oozie_Workflow_Test ooziewf_test.out      ERROR           42
Hive_Metastore_Test metastore_test.out   ERROR          14
Hive_Server_2_Test hiveserver2_test.out   ERROR           8
WebHCat_Test webhcat_test.out              ERROR        139
HttpFS_Test httpfs_test.out                    SUCCESS       8
Orabalancer_Test balancer_test.out          ERROR          17
Spark_Test spark_test.out                      SUCCESS       19
Spark2_Test spark2_test.out                   ERROR          15
ORAAH_Test oraah_test.out                    ERROR         182
Total time : 321 sec.


Additionally the output logs show a problem with oracle user access to the HDFS /tmp directory  like below:

log4j:ERROR Either File or DatePattern options are not set for appender [DRFA].
Exception in thread "main" java.lang.RuntimeException: Permission denied: user=oracle, access=EXECUTE, inode="/tmp":hdfs:supergroup:d-wx------
at org.apache.hadoop.hdfs.server.namenode.DefaultAuthorizationProvider.checkFsPermission(DefaultAuthoriza
at org.apache.hadoop.hdfs.server.namenode.DefaultAuthorizationProvider.check(DefaultAuthorizationProvider .java:260)

Caused by: Permission denied: user=oracle, access=EXECUTE, inode="/tmp":hdfs:supergroup:d-wx------


Note: This will not impact BDA V4.12 upgrades because the HDFS /tmp is already created with the correct permissions and Mammoth upgrade should not change them.



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.