Configuring BDA to Communicate with Exadata via JDBC and SDP Causes Issues with Hadoop. (Doc ID 1967298.1)

Last updated on FEBRUARY 16, 2015

Applies to:

Big Data Appliance Integrated Software - Version 4.0 and later
Linux x86-64

Symptoms

Setting the environment variable LD_PRELOAD="libsdp.so" is causing errors within the environment running Hadoop shell commands.

# hadoop fs -ls /user/oracle/testdir
dir: /tmp/libsdp.log.130 file: /tmp/libsdp.log.130/log
dir: /tmp/libsdp.log.130 file: /tmp/libsdp.log.130/log
/u01/app/bda/cdh/hadoop-2.3.0-cdh5.1.2/share/hadoop/mapreduce1/bin/hadoop: line 50: cd: dir: /tmp/libsdp.log.130 file: /tmp/libsdp.log.130/log
/u01/app/bda/cdh/hadoop-2.3.0-cdh5.1.2/share/hadoop/mapreduce1/bin: No such file or directory
/u01/app/bda/cdh/hadoop-2.3.0-cdh5.1.2/share/hadoop/mapreduce1/bin/hadoop: line 52: /u01/app/oracle/hadoop-config.sh: No such file or directory
dir: /tmp/libsdp.log.130 file: /tmp/libsdp.log.130/log
dir: /tmp/libsdp.log.130 file: /tmp/libsdp.log.130/log
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
15/01/15 11:06:14 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
Found 1 items

 

Changes

 Configuring JDBC for SDP per the Oracle documentation at http://docs.oracle.com/cd/E55905_01/doc.40/e55814/exadata.htm#BIGUG261 it instructs you to set the LD_PRELOAD environment variable to "libsdp.so".

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms