[teiid-issues] [JBoss JIRA] (TEIID-2730) Cannot query Sybase database with jconn3.jar

Steven Hawkins (JIRA) jira-events at lists.jboss.org
Fri Nov 8 06:55:01 EST 2013


     [ https://issues.jboss.org/browse/TEIID-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins updated TEIID-2730:
----------------------------------

        Summary: Cannot query Sybase database with jconn3.jar  (was: Cannot connect to Sybase database with jconn3.jar)
    Component/s: JDBC Connector


This is an issue with the metadata.  In particular it looks like Sybase (possibly depending upon the driver version) does not want a quoted catalog name.  If using a dynamic vdb, you can instruct Teiid to not use the catalog name or to not quote the name in source.

So in Designer you need to have it handle the name in source differently to query correctly.
                
> Cannot query Sybase database with jconn3.jar
> --------------------------------------------
>
>                 Key: TEIID-2730
>                 URL: https://issues.jboss.org/browse/TEIID-2730
>             Project: Teiid
>          Issue Type: Bug
>          Components: JDBC Connector
>    Affects Versions: 8.4
>         Environment: java oracle 1.7, Teiid 8.4.1-redhat4 in DV 6.0.0.ER3, Teiid Designer 8.3.beta3
>            Reporter: Lucie Fabrikova
>            Assignee: Steven Hawkins
>         Attachments: bqtHNB.vdb, bqt_HNB.xmi, jconn3.jar
>
>
> In teiid designer, I created a connection profile to Sybase database with URL jdbc:sybase:Tds:vmg07.mw.lab.eng.bos.redhat.com:5000/bqt2 and driver jconn3.jar.
> I created a relational source model from the jdbc connection and VDB with the source model. Then I deployed the VDB and executed query select * from "bqt_HNB"."g1" which resulted in this error message:
> TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 bqt_HNB: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]
> Console:
> OPTIMIZATION COMPLETE:
> PROCESSOR PLAN:
> AccessNode(0) output=[bqt_HNB.g1.e1, bqt_HNB.g1.e2] SELECT g_0.e1, g_0.e2 FROM bqt_HNB.g1 AS g_0
> ============================================================================
> 10:55:07,362 INFO  [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) SybaseExecutionFactory Commit=true;DatabaseProductName=Adaptive Server Enterprise;DatabaseProductVersion=Adaptive Server Enterprise/15.0.3/EBF 16549 ESD#1/P/x86_64/Enterprise Linux/ase1503/2681/64-bit/FBO/Mon Mar  9 04:10:47 2009;DriverMajorVersion=6;DriverMajorVersion=0;DriverName=jConnect (TM) for JDBC (TM);DriverVersion=jConnect (TM) for JDBC(TM)/6.05(Build 26564)/P/EBF16903/JDK14/Sun May 31  1:05:35 2009;IsolationLevel=2
> 10:55:07,555 WARN  [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) Connector worker process failed for atomic-request=dg2FpIhALlUI.0.0.0: org.teiid.translator.jdbc.JDBCExecutionException: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]
> 	at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:88)
> 	at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:254) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> 	at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:444) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> 	at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:157) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> 	at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:154) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_45]
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_45]
> 	at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> 	at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> 	at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> 	at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45]
> 	at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]
> Caused by: com.sybase.jdbc3.jdbc.SybSQLException: Incorrect syntax near 'e1'.
> 	at com.sybase.jdbc3.tds.Tds.a(Unknown Source)
> 	at com.sybase.jdbc3.tds.Tds.nextResult(Unknown Source)
> 	at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source)
> 	at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
> 	at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
> 	at com.sybase.jdbc3.jdbc.SybStatement.queryLoop(Unknown Source)
> 	at com.sybase.jdbc3.jdbc.SybStatement.executeQuery(Unknown Source)
> 	at com.sybase.jdbc3.jdbc.SybPreparedStatement.executeQuery(Unknown Source)
> 	at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
> 	at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:84)
> 	... 13 more
> 10:55:07,568 WARN  [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2) TEIID30020 Processing exception for request dg2FpIhALlUI.0 'TEIID30504 bqt_HNB: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]'. Originally TeiidProcessingException 'Incorrect syntax near 'e1'.
> ' com.sybase.jdbc3.tds.Tds.a(Unknown Source). Enable more detailed logging to see the entire stacktrace.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the teiid-issues mailing list