My Oracle Support Banner

After Upgrade from BDA 4.13 to BDA 5.1.0 Sqoop Jobs Failing with Error: "Exception in thread "main" java.lang.UnsatisfiedLinkError (Doc ID 2688658.1)

Last updated on JULY 30, 2020

Applies to:

Big Data Appliance Integrated Software - Version 5.1.0 and later
Information in this document applies to any platform.

Symptoms

Upgraded BDA cluster from 4.13/ CDH 5.15.1 to BDA 5.1.0 /CDH 6.2.1. After upgrading the cluster, Sqoop jobs are failing with an exception error:

 

[INFO]: RUNNING CMD
[INFO]:1 has been generated
[INFO]: GETTING SQOOP STATS
[INFO]:----Start: Warning: /opt/cloudera/parcels/CDH-6.2.1-
1.cdh6.2.1.p0.1580995/bin/../lib/sqoop/../accumulo does not exist! Accumulo imports will fail.
Please set $ACCUMULO_HOME to the root of your Accumulo installation.
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/opt/cloudera/parcels/CDH-6.2.1-1.cdh6.2.1.p0.1580995/jars/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/opt/cloudera/parcels/CDH-6.2.1-1.cdh6.2.1.p0.1580995/jars/log4j-slf4j-impl-2.8.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
<YY/MM/DD> <TIMESTAMP> INFO sqoop.Sqoop: Running Sqoop version: 1.4.7-cdh6.2.1
<YY/MM/DD> <TIMESTAMP> INFO manager.SqlManager: Using default fetchSize of 1000
Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /opt/cloudera/sqoop/sybase/lib32/libdbjdbc12.so.1 which might have disabled stack guard. The VM will try to fix the stack guard now.
It's highly recommended that you fix the library with 'execstack -c ', or link it with '-z noexecstack'.
Exception in thread "main" java.lang.UnsatisfiedLinkError:
/opt/cloudera/sqoop/sybase/lib64/libdbjdbc12.so.1: libdbtasks12_r.so: cannot open shared object file: No such file or directory
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1934)

 
The jobs are being run from a client / edge node and these same jobs worked without error prior to the upgrade.

Cause

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
Symptoms
Cause
Solution
References


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