Hi Artem, I was hoping for another classloader exception, which causes the one you pasted. In logs it might be immediately below this exception, or above.
If not, the only other thing I could find is about '-driver' and connection managers - https://issues.apache.org/jira/browse/SQOOP-626. Regards, Srimanth On Thu, Jul 25, 2013 at 10:17 AM, Artem Ervits <[email protected]> wrote: > The full error is:**** > > ** ** > > 13/07/24 15:07:06 WARN tool.BaseSqoopTool: Setting your password on the > command-line is insecure. Consider using -P instead.**** > > 13/07/24 15:07:06 WARN sqoop.ConnFactory: Parameter --driver is set to an > explicit driver however appropriate connection manager is not being set > (via --connection-manager). Sqoop is going to fall back to > org.apache.sqoop.manager.GenericJdbcManager. Please specify explicitly > which connection manager should be used next time.**** > > 13/07/24 15:07:06 INFO manager.SqlManager: Using default fetchSize of 1000 > **** > > 13/07/24 15:07:06 INFO tool.CodeGenTool: Beginning code generation**** > > 13/07/24 15:07:06 ERROR sqoop.Sqoop: Got exception running Sqoop: > java.lang.RuntimeException: Could not load db driver class: > com.ibm.db2.jcc.DB2Driver**** > > java.lang.RuntimeException: Could not load db driver class: > com.ibm.db2.jcc.DB2Driver**** > > at > org.apache.sqoop.manager.SqlManager.makeConnection(SqlManager.java:636)*** > * > > at > org.apache.sqoop.manager.GenericJdbcManager.getConnection(GenericJdbcManager.java:52) > **** > > at org.apache.sqoop.manager.SqlManager.execute(SqlManager.java:525) > **** > > at org.apache.sqoop.manager.SqlManager.execute(SqlManager.java:548) > **** > > at > org.apache.sqoop.manager.SqlManager.getColumnTypesForRawQuery(SqlManager.java:191) > **** > > at > org.apache.sqoop.manager.SqlManager.getColumnTypesForQuery(SqlManager.java:182) > **** > > at > org.apache.sqoop.manager.ConnManager.getColumnTypes(ConnManager.java:271)* > *** > > at > org.apache.sqoop.orm.ClassWriter.getColumnTypes(ClassWriter.java:1235)**** > > at org.apache.sqoop.orm.ClassWriter.generate(ClassWriter.java:1060) > **** > > at > org.apache.sqoop.tool.CodeGenTool.generateORM(CodeGenTool.java:82)**** > > at > org.apache.sqoop.tool.ImportTool.importTable(ImportTool.java:390)**** > > at org.apache.sqoop.tool.ImportTool.run(ImportTool.java:476)**** > > at org.apache.sqoop.Sqoop.run(Sqoop.java:145)**** > > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)**** > > at org.apache.sqoop.Sqoop.runSqoop(Sqoop.java:181)**** > > at org.apache.sqoop.Sqoop.runTool(Sqoop.java:220)**** > > at org.apache.sqoop.Sqoop.runTool(Sqoop.java:229)**** > > at org.apache.sqoop.Sqoop.main(Sqoop.java:238)**** > > ** ** > > ** ** > > *From:* Srimanth Gunturi [mailto:[email protected]] > *Sent:* Thursday, July 25, 2013 1:12 PM > *To:* [email protected] > *Subject:* Re: Problem seeing DB2 jars when calling sqoop with Ambari > provisioned cluster**** > > ** ** > > Hi Artem,**** > > Is there more on the exception as to why the class could not be loaded? ** > ** > > Was the class not found, or class binary incompatibility, etc...**** > > I am guessing the JARs are readable for user launching sqoop.**** > > Regards,**** > > Srimanth**** > > ** ** > > ** ** > > ** ** > > ** ** > > On Thu, Jul 25, 2013 at 7:58 AM, Artem Ervits <[email protected]> wrote:**** > > Hello all,**** > > **** > > I am having trouble running sqoop with DB2 driver on a client machine > provisioned by Ambari. I placed the db2 jars into /usr/lib/sqoop/lib and > when I try to do an import I’m getting the following error:**** > > **** > > 13/07/24 15:07:06 ERROR sqoop.Sqoop: Got exception running Sqoop: > java.lang.RuntimeException: Could not load db driver class: > com.ibm.db2.jcc.DB2Driver**** > > java.lang.RuntimeException: Could not load db driver class: > com.ibm.db2.jcc.DB2Driver**** > > at > org.apache.sqoop.manager.SqlManager.makeConnection(SqlManager.java:636)*** > * > > **** > > **** > > Do I need to push the jars via the Ambari server? If so, how is that done? > **** > > **** > > Thank you**** > > > This electronic message is intended to be for the use only of the named > recipient, and may contain information that is confidential or privileged. > If you are not the intended recipient, you are hereby notified that any > disclosure, copying, distribution or use of the contents of this message is > strictly prohibited. If you have received this message in error or are not > the named recipient, please notify us immediately by contacting the sender > at the electronic mail address noted above, and delete and destroy all > copies of this message. Thank you.**** > > ** ** > > This electronic message is intended to be for the use only of the named > recipient, and may contain information that is confidential or privileged. > If you are not the intended recipient, you are hereby notified that any > disclosure, copying, distribution or use of the contents of this message is > strictly prohibited. If you have received this message in error or are not > the named recipient, please notify us immediately by contacting the sender > at the electronic mail address noted above, and delete and destroy all > copies of this message. Thank you. >
