Member since
01-20-2015
1
Post
0
Kudos Received
0
Solutions
02-05-2015
05:46 PM
We overcame the issue, Sqoop2 Service would not start after upgrade, by removing jars (from /var/lib/sqoop2 ) pulled from the Web/latest Apache Derby libs which were a MUST for Sqoop Upgrade then restarting Sqoop Service. I ran into issue during upgrade: 5.1.0 to 5.3.0 Latest Apache Derby libs, derbyclient.jar and derby.jar which I pulled from the Web, as per earlier suggestion, took care of the upgrade bug. But the service would not start. Not until we removed those manually placed for upgrade libraries from /var/lib/sqoop2. Once removed Sqoop service started up just fine. We had case open with Cloudera: 51398 in case you interested. /var/log/sqoop2/derbyrepo.log: start up error Mon Jan 26 13:06:59 PST 2015 Thread[main,5,main] Mon Jan 26 13:06:59 PST 2015 Thread[main,5,main] Startup failed due to missing functionality for org.apache.derby.jdbc.InternalDriver. Please ensure your classpath includes the correct Derby software. ERROR XBM02: Startup failed due to missing functionality for org.apache.derby.jdbc.InternalDriver. Please ensure your classpath includes the correct Derby software. at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.iapi.services.monitor.Monitor.missingImplementation(Unknown Source) at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown Source) at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(Unknown Source) at org.apache.derby.impl.services.monitor.BaseMonitor.startServices(Unknown Source) at org.apache.derby.impl.services.monitor.BaseMonitor.runWithState(Unknown Source) at org.apache.derby.impl.services.monitor.FileMonitor.<init>(Unknown Source) at org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Unknown Source) at org.apache.derby.iapi.jdbc.JDBCBoot.boot(Unknown Source) at org.apache.derby.jdbc.EmbeddedDriver.boot(Unknown Source) at org.apache.derby.jdbc.EmbeddedDriver.<clinit>(Unknown Source) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:190) at org.apache.sqoop.utils.ClassUtils.loadClass(ClassUtils.java:47) at org.apache.sqoop.repository.JdbcRepositoryProvider.initializeRepositoryHandler(JdbcRepositoryProvider.java:122) at org.apache.sqoop.repository.JdbcRepositoryProvider.initialize(JdbcRepositoryProvider.java:65) at org.apache.sqoop.repository.RepositoryManager.initialize(RepositoryManager.java:119) at org.apache.sqoop.repository.RepositoryManager.initialize(RepositoryManager.java:77) at org.apache.sqoop.core.SqoopServer.initialize(SqoopServer.java:53) at org.apache.sqoop.server.ServerInitializer.contextInitialized(ServerInitializer.java:41) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4210) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4709) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:583) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504) var/log/sqoop2: upgrade error 2015-01-26 14:52:11,040 ERROR org.apache.sqoop.tools.tool.UpgradeTool: Can't finish upgrading RepositoryManager, Driver and ConnectionManager: org.apache.sqoop.common.SqoopException: JDBCREPO_0007:Unable to lease link at org.apache.sqoop.repository.JdbcRepositoryTransaction.begin(JdbcRepositoryTransaction.java:63) at org.apache.sqoop.repository.JdbcRepository.doWithConnection(JdbcRepository.java:85) at org.apache.sqoop.repository.JdbcRepository.doWithConnection(JdbcRepository.java:61) at org.apache.sqoop.repository.JdbcRepository.createOrUpgradeRepository(JdbcRepository.java:127) at org.apache.sqoop.repository.RepositoryManager.initialize(RepositoryManager.java:123) at org.apache.sqoop.tools.tool.UpgradeTool.runToolWithConfiguration(UpgradeTool.java:39) at org.apache.sqoop.tools.ConfiguredTool.runTool(ConfiguredTool.java:35) at org.apache.sqoop.tools.ToolRunner.main(ToolRunner.java:75) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.sqoop.tomcat.TomcatToolRunner.main(TomcatToolRunner.java:77) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.catalina.startup.Tool.main(Tool.java:225) Caused by: java.sql.SQLException: No suitable driver found for jdbc:derby:/var/lib/sqoop2/repository/db;create=true at java.sql.DriverManager.getConnection(DriverManager.java:596) at java.sql.DriverManager.getConnection(DriverManager.java:187) at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:51) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:840) at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95) at org.apache.sqoop.repository.JdbcRepositoryTransaction.begin(JdbcRepositoryTransaction.java:61) ... 17 more 2015-01-26 14:52:11,043 INFO org.apache.sqoop.core.PropertiesConfigurationProvider: Shutting down configuration poller thread
... View more