November 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2730) Cannot connect to Sybase database with jconn3.jar

by Lucie Fabrikova (JIRA)

Lucie Fabrikova created TEIID-2730: -------------------------------------- Summary: Cannot connect to Sybase database with jconn3.jar Key: TEIID-2730 URL: https://issues.jboss.org/browse/TEIID-2730 Project: Teiid Issue Type: Bug 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 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2729) Dynamic VDB xml requires sibling elements to be in a certain order

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2729?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2729: ------------------------------------- This XML is backed by schema, that is how it enforces it. > Dynamic VDB xml requires sibling elements to be in a certain order > ------------------------------------------------------------------ > > Key: TEIID-2729 > URL: https://issues.jboss.org/browse/TEIID-2729 > Project: Teiid > Issue Type: Enhancement > Components: AdminApi > Affects Versions: 8.5 > Reporter: Mark Drilling > Assignee: Steven Hawkins > > In my *-vdb.xml, I have a model defined per following snippet: > <model name="myModel" type="PHYSICAL" visible="true"> > <source name="myModel" translator-name="hive" connection-jndi-name="Hive12Src" /> > <property name="trimColumnNames" value="true" /> > </model> > The vdb.xml failed to parse, so I moved the <property> element ahead of <source> and then it worked. > I don't think element ordering should matter in this case? -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2729) Dynamic VDB xml requires sibling elements to be in a certain order

by Mark Drilling (JIRA)

Mark Drilling created TEIID-2729: ------------------------------------ Summary: Dynamic VDB xml requires sibling elements to be in a certain order Key: TEIID-2729 URL: https://issues.jboss.org/browse/TEIID-2729 Project: Teiid Issue Type: Enhancement Components: AdminApi Affects Versions: 8.5 Reporter: Mark Drilling Assignee: Steven Hawkins In my *-vdb.xml, I have a model defined per following snippet: <model name="myModel" type="PHYSICAL" visible="true"> <source name="myModel" translator-name="hive" connection-jndi-name="Hive12Src" /> <property name="trimColumnNames" value="true" /> </model> The vdb.xml failed to parse, so I moved the <property> element ahead of <source> and then it worked. I don't think element ordering should matter in this case? -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2714) Buffer defrag not working

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2714?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2714: --------------------------------------- added org.teiid.compactBufferFiles system property to the admin guide to keep more compact buffer file, defaults to false. This could be tweaked further as the defrag/truncate cycle is initiated after 2^14 block removals. Given that a typical allocation is around 64k this should reclaim space after a turn over of several hundred megs to a gig (note that we'll be somewhat compact already since we assign blocks from the start of the files). > Buffer defrag not working > ------------------------- > > Key: TEIID-2714 > URL: https://issues.jboss.org/browse/TEIID-2714 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6, 7.7.9 > > > The defrag task is not working as expected because the header values are written by an object output stream - and not as standalone values into the block data. > For most data usage patterns this isn't an issue as the storage files are self compacting over time due to low block assignments. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2707) proactive buffering on an enhanced sort merge left outer join results in an assertionerror

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2707?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2707: --------------------------------- Fix Version/s: 7.7.9 > proactive buffering on an enhanced sort merge left outer join results in an assertionerror > ------------------------------------------------------------------------------------------ > > Key: TEIID-2707 > URL: https://issues.jboss.org/browse/TEIID-2707 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.6, 7.7.9 > > > The proactive buffering logic with particular blocking patterns is not correct. Namely the setting of the buffer to forward only prevents re-reading which results in an AssertionError. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2707) proactive buffering on an enhanced sort merge left outer join results in an assertionerror

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2707?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2707: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1028027, https://bugzilla.redhat.com/show_bug.cgi?id=1028116 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1028027) > proactive buffering on an enhanced sort merge left outer join results in an assertionerror > ------------------------------------------------------------------------------------------ > > Key: TEIID-2707 > URL: https://issues.jboss.org/browse/TEIID-2707 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.6 > > > The proactive buffering logic with particular blocking patterns is not correct. Namely the setting of the buffer to forward only prevents re-reading which results in an AssertionError. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2714) Buffer defrag not working

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2714?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2714: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1028023|https://bugzilla.redhat.com/show_bug.cgi?id=1028023] from ASSIGNED to MODIFIED > Buffer defrag not working > ------------------------- > > Key: TEIID-2714 > URL: https://issues.jboss.org/browse/TEIID-2714 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6, 7.7.9 > > > The defrag task is not working as expected because the header values are written by an object output stream - and not as standalone values into the block data. > For most data usage patterns this isn't an issue as the storage files are self compacting over time due to low block assignments. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2728) Very large sorts are inefficient

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2728?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2728: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1028016|https://bugzilla.redhat.com/show_bug.cgi?id=1028016] from ASSIGNED to MODIFIED > Very large sorts are inefficient > -------------------------------- > > Key: TEIID-2728 > URL: https://issues.jboss.org/browse/TEIID-2728 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.6 > > > This is a regression of TEIID-2429. When the memory space needed for a sort is estimated to be above 2 GB, the expression used (even though it's assigned to a long) will overflow. This then causes the processing to use the batch size as the intermediate sort buffer size, which for any high row count will lead to many passes (the logic typically should achieve at most a two pass sort). -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2707) proactive buffering on an enhanced sort merge left outer join results in an assertionerror

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2707?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2707: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1028027|https://bugzilla.redhat.com/show_bug.cgi?id=1028027] from ASSIGNED to MODIFIED > proactive buffering on an enhanced sort merge left outer join results in an assertionerror > ------------------------------------------------------------------------------------------ > > Key: TEIID-2707 > URL: https://issues.jboss.org/browse/TEIID-2707 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.6 > > > The proactive buffering logic with particular blocking patterns is not correct. Namely the setting of the buffer to forward only prevents re-reading which results in an AssertionError. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2707) proactive buffering on an enhanced sort merge left outer join results in an assertionerror

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2707?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2707: --------------------------------------- Refined the previous commit to account for sources that do not block - otherwise the collection during prefetch could simply pull all batches. > proactive buffering on an enhanced sort merge left outer join results in an assertionerror > ------------------------------------------------------------------------------------------ > > Key: TEIID-2707 > URL: https://issues.jboss.org/browse/TEIID-2707 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.6 > > > The proactive buffering logic with particular blocking patterns is not correct. Namely the setting of the buffer to forward only prevents re-reading which results in an AssertionError. -- 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

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2013