Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

[Simba][ImpalaJDBCDriver](500051) The table "xxx" could not be found

avatar
Expert Contributor

Hi,

 

We have set the HA proxy load balancer with impala daemons recently and trying to run some queries through our application using JDBC connection. Its working fine, but sometimes it throws us error like following--------------

 

But when I run the query individually aganist each Impala daemon it works fine, with no issue and is able to find the table.

 

The config of HA proxy includes hostnames where all IMPALA DaEMONS are residing. so no issue here, but not understanding why its causing this error.

 

Please help urgently !!!!

 

 

ERROR:

 

1449694771535:get_manager_teams.xactionSQLBaseComponent.ERROR_0006 - Could not execute get_manager_teams.xaction
java.sql.SQLException: [Simba][ImpalaJDBCDriver](500051) ERROR processing query/statement. Error Code: [Simba][JSQLEngine](12010) The table "xxxxx" could not be found., SQL state: HY000, Query:

 

(xxxxxxxx----query resides here which is simple select)

 


.
at com.cloudera.impala.hivecommon.dataengine.HiveJDBCDataEngine.prepare(Unknown Source)
at com.cloudera.impala.jdbc.common.SStatement.executeNoParams(Unknown Source)
at com.cloudera.impala.jdbc.common.SStatement.executeQuery(Unknown Source)
at com.mchange.v2.c3p0.impl.NewProxyStatement.executeQuery(NewProxyStatement.java:35)
at org.pentaho.platform.plugin.services.connections.sql.SQLConnection.executeQuery(SQLConnection.java:375)
at org.pentaho.platform.plugin.services.connections.sql.SQLConnection.executeQuery(SQLConnection.java:332)
at org.pentaho.platform.plugin.action.sql.SQLBaseComponent.doQuery(SQLBaseComponent.java:649)
at org.pentaho.platform.plugin.action.sql.SQLBaseComponent.runQuery(SQLBaseComponent.java:559)
at org.pentaho.platform.plugin.action.sql.SQLBaseComponent.executeAction(SQLBaseComponent.java:257)
at org.pentaho.platform.engine.services.solution.ComponentBase.execute(ComponentBase.java:463)
at org.pentaho.platform.engine.services.runtime.RuntimeContext.executeComponent(RuntimeContext.java:1293)
at org.pentaho.platform.engine.services.runtime.RuntimeContext.executeAction(RuntimeContext.java:1262)
at org.pentaho.platform.engine.services.runtime.RuntimeContext.performActions(RuntimeContext.java:1161)
at org.pentaho.platform.engine.services.runtime.RuntimeContext.executeLoop(RuntimeContext.java:1105)
at org.pentaho.platform.engine.services.runtime.RuntimeContext.executeSequence(RuntimeContext.java:987)
at org.pentaho.platform.engine.services.runtime.RuntimeContext.performActions(RuntimeContext.java:1154)
at org.pentaho.platform.engine.services.runtime.RuntimeContext.executeLoop(RuntimeContext.java:1105)
at org.pentaho.platform.engine.services.runtime.RuntimeContext.executeSequence(RuntimeContext.java:987)
at org.pentaho.platform.engine.services.runtime.RuntimeContext.executeSequence(RuntimeContext.java:897)
at org.pentaho.platform.engine.services.solution.SolutionEngine.executeInternal(SolutionEngine.java:399)
at org.pentaho.platform.engine.services.solution.SolutionEngine.execute(SolutionEngine.java:317)
at org.pentaho.platform.engine.services.solution.SolutionEngine.execute(SolutionEngine.java:193)
at org.pentaho.platform.engine.services.BaseRequestHandler.handleActionRequest(BaseRequestHandler.java:159)
at org.pentaho.platform.engine.services.solution.SolutionHelper.doActionInternal(SolutionHelper.java:310)
at org.pentaho.platform.engine.services.solution.SolutionHelper.doAction(SolutionHelper.java:295)
at com.collectivei.rest.analyticaldataasservice.utils.CIServiceUtil.getXactionResultString(CIServiceUtil.java:284)
at com.collectivei.rest.analyticaldataasservice.utils.CIServiceUtil.getXactionResultString(CIServiceUtil.java:269)
at com.collectivei.rest.analyticaldataasservice.utils.CIServiceUtil.getManagerTeams(CIServiceUtil.java:1357)
at com.collectivei.rest.analyticaldataasservice.utils.CIServiceUtil.getManagerTeams(CIServiceUtil.java:1352)
at com.collectivei.rest.analyticaldataasservice.utils.ESUtils.loadDataToES(ESUtils.java:208)
at com.collectivei.rest.analyticaldataasservice.utils.ESUtils.createESStoreAfterWinProbabilityNotification(ESUtils.java:122)
at com.collectivei.rest.analyticaldataasservice.cache.CIWinProbabilityNotificationCacheBuilder.buildCache(CIWinProbabilityNotificationCacheBuilder.java:26)
Caused by: com.cloudera.impala.support.exceptions.GeneralException: [Simba][ImpalaJDBCDriver](500051) ERROR processing query/statement. Error Code: [Simba][JSQLEngine](12010) The table "xxxxx" could not be found., SQL state: HY000, Query:

.
... 32 more
2015-12-09 20:59:31,582 ERROR v2 48f985d3-e8d1-4a27-90f7-8bc1092f90f7 10.110.1.98 adas-a9bc9c7c-762f-4e40-956c-0d85f258aa69 [org.pentaho.platform.plugin.action.sql.SQLLookupRule] Error end:

 

 

 

 

1 REPLY 1

avatar
Cloudera Employee

Hi Jais,

 

The error appears to come from the Simba's JDBC driver code instead of Impala. You might try contacting Simba for help. Also the driver has a native mode, enabling the UseNativeQuery option may help by bypassing some driver side processing.

 

If you see any errors in the impalad or catalogd logs please post them. Or if you have a consistent way to reproduce the error, we can work with Simba on the problem.

 

Casey