November 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-1808) Cannot load metadata for dynamic VDB on oracle10g

by Steven Hawkins (Closed) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1808?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1808. --------------------------------- > Cannot load metadata for dynamic VDB on oracle10g > ------------------------------------------------- > > Key: TEIID-1808 > URL: https://issues.jboss.org/browse/TEIID-1808 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.4.1 > Reporter: Filip Nguyen > Assignee: Steven Hawkins > Attachments: mytext-ds.xml, myvdb-vdb.xml, server.log > > > There seems to be a problem with deploying dynamic VDB (attachment) which loads metadata from Oracle10g. It works on any other database supported by SOA P (including Oracle11g). > When I deploy the VDB I get: > {code:title=Server.log|borderStyle=solid} > 2011-11-03 10:32:26,306 INFO [org.teiid.RUNTIME] (JBoss System Threads(1)-7) VDB myvdb.1 model EMPLOYEES metadata is currently being loaded. Start Time: 11/3/11 10:32 AM > 2011-11-03 10:32:26,306 INFO [org.teiid.RUNTIME] (JBoss System Threads(1)-8) VDB myvdb.1 model TextFileData metadata is currently being loaded. Start Time: 11/3/11 10:32 AM > 2011-11-03 10:32:26,307 INFO [org.teiid.RUNTIME] (HDScanner) VDB "myvdb.1[EMPLOYEES[oracle-connector/oracle/java:DefaultDS], TextFileData[text-connector/file/java:TxtFileDS]]" deployed in inactive state. > 2011-11-03 10:32:26,307 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] (HDScanner) Fully Deployed vfsfile:/home/fnguyen/work/soaplatform/products/esb/jboss-as/server/oracle10g/deploy/myvdb-vdb.xml > 2011-11-03 10:32:26,323 INFO [org.teiid.RUNTIME] (JBoss System Threads(1)-8) VDB myvdb.1 model TextFileData metadata is currently being loaded. > .... > .... > 2011-11-03 10:35:04,832 WARN [org.teiid.RUNTIME] (JBoss System Threads(1)-7) myvdb.1 is now "incomplete", because model "EMPLOYEES" can not retrieve metadata. Please fix any errors and re-deploy relevant DataSources and/or the VDB. > {code} > In web console VDB is not active and contains following errors: > {code:title=Web console|borderStyle=solid} > ERROR VDB myvdb.1 model employees metadata is currently being loaded. Start Time: 11/3/11 10:54 AM > ERROR myvdb.1 is now "incomplete", because model "employees" can not retrieve metadata. Please fix any errors and re-deploy relevant DataSources and/or the VDB. > ERROR Teiid runtime names, which are case insensitive, for the imported metadata are not unique. If not already set, use the setting importer.useFullSchemaName to create Teiid names that include the source schema. > {code} > It looks like there is a problem with content of the database, but I only created one database table: > {code:title=Employees table|borderStyle=solid} > -------------------------------------------------------- > -- DDL for Table employees > -------------------------------------------------------- > CREATE TABLE "SOAESB1"."employees" > ( "ID" NUMBER(19,0), > "NAME" VARCHAR2(255 CHAR), > "SURNAME" VARCHAR2(255 CHAR), > "SYMBOL" VARCHAR2(255 CHAR) > ) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING > STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 > PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) > TABLESPACE "USERS" ; > -------------------------------------------------------- > -- DDL for Index SYS_C00330055 > -------------------------------------------------------- > CREATE UNIQUE INDEX "SOAESB1"."SYS_C00330055" ON "SOAESB1"."employees" ("ID") > PCTFREE 10 INITRANS 2 MAXTRANS 255 > STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 > PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) > TABLESPACE "USERS" ; > -------------------------------------------------------- > -- Constraints for Table employees > -------------------------------------------------------- > ALTER TABLE "SOAESB1"."employees" MODIFY ("ID" NOT NULL ENABLE); > > ALTER TABLE "SOAESB1"."employees" ADD PRIMARY KEY ("ID") > USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 > STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 > PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) > TABLESPACE "USERS" ENABLE; > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1762) Exception when using Teiid with BIRT Report Designer

by Graeme Gillies (JIRA)

Exception when using Teiid with BIRT Report Designer ---------------------------------------------------- Key: TEIID-1762 URL: https://issues.jboss.org/browse/TEIID-1762 Project: Teiid Issue Type: Bug Affects Versions: 7.5 Environment: java-1.6.0-openjdk-1.6.0.0-59.1.10.3.fc15.i686 java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.3) (fedora-59.1.10.3.fc15-i386) OpenJDK Server VM (build 20.0-b11, mixed mode) On Fedora 15 Eclipse version Helios, using Birt version 3.7 milestone. Connecting to teiid 7.5 (in JBoss EAP 5.1.1) running on RHEL 5 Reporter: Graeme Gillies Assignee: Steven Hawkins Hi, I've been trying to use the Birt report Designer tool in eclipse to talk to teiid in order to look at designing some reports on top of it. I can add the datasource fine but when I go to create a data set, I notice the following error getting spammed to the eclipse log {code} Sep 26, 2011 12:00:39 PM org.eclipse.birt.report.data.oda.jdbc.ui.model.SchemaNode refetchChildren WARNING: Column name "TABLE_NAME" does not exist. org.teiid.jdbc.TeiidSQLException: Column name "TABLE_NAME" does not exist. at org.teiid.jdbc.ResultSetImpl.findColumnIndex(ResultSetImpl.java:1227) at org.teiid.jdbc.ResultSetImpl.findColumn(ResultSetImpl.java:1214) at org.teiid.jdbc.ResultSetImpl.getString(ResultSetImpl.java:826) at org.eclipse.birt.report.data.oda.jdbc.ui.model.SchemaNode.refetchChildren(SchemaNode.java:71) at org.eclipse.birt.report.data.oda.jdbc.ui.model.RootNode.refetchChildren(RootNode.java:106) at org.eclipse.birt.report.data.oda.jdbc.ui.model.ChildrenAllowedNode$1TempThread.run(ChildrenAllowedNode.java:35) Sep 26, 2011 12:00:54 PM org.eclipse.birt.report.data.oda.jdbc.ui.model.SchemaNode refetchChildren WARNING: Column name "TABLE_NAME" does not exist. org.teiid.jdbc.TeiidSQLException: Column name "TABLE_NAME" does not exist. at org.teiid.jdbc.ResultSetImpl.findColumnIndex(ResultSetImpl.java:1227) at org.teiid.jdbc.ResultSetImpl.findColumn(ResultSetImpl.java:1214) at org.teiid.jdbc.ResultSetImpl.getString(ResultSetImpl.java:826) at org.eclipse.birt.report.data.oda.jdbc.ui.model.SchemaNode.refetchChildren(SchemaNode.java:71) at org.eclipse.birt.report.data.oda.jdbc.ui.model.RootNode.refetchChildren(RootNode.java:106) at org.eclipse.birt.report.data.oda.jdbc.ui.model.ChildrenAllowedNode$1TempThread.run(ChildrenAllowedNode.java:35) {code} We have also noticed the problem when using other reporting engines like http://datavision.sourceforge.net/ which throw the same error. Is it possible to have the column added to whatever table is needed (I assume the SYS model) in order for these errors to not occur? Thanks, Graeem -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
6
0 / 0

[JBoss JIRA] (TEIID-1774) Ingres as source - ORDER BY on TimeValue not properly ordering results as expected

by Steven Hawkins (Closed) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1774?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1774. --------------------------------- > Ingres as source - ORDER BY on TimeValue not properly ordering results as expected > ---------------------------------------------------------------------------------- > > Key: TEIID-1774 > URL: https://issues.jboss.org/browse/TEIID-1774 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 7.4.1 > Reporter: Warren Gibson > Assignee: Steven Hawkins > > EDS Query Testing is getting unexpected results on 68 queries involving ORDER BY on TimeValue. When an ORDER BY is placed on TimeValue the returned results are not ordered as expected. > An example query is: SELECT BQT1.SmallA.TimeValue FROM BQT1.SmallA ORDER BY TimeValue > The returned results are: > TimeValue > 05:00:00 > 05:00:00 > 06:00:00 > 06:00:00 > 07:00:00 > 08:00:00 > 08:00:00 > 09:00:00 > 09:00:00 > 10:00:00 > 10:00:00 > 11:00:00 > 11:00:00 > 12:00:00 > 12:00:00 > 13:00:00 > 13:00:00 > 14:00:00 > 14:00:00 > 15:00:00 > 16:00:00 > 16:00:00 > 17:00:00 > 17:00:00 > 18:00:00 > 18:00:00 > 19:00:00 > 19:00:00 > 20:00:00 > 20:00:00 > 21:00:00 > 21:00:00 > 22:00:00 > 22:00:00 > 23:00:00 > 00:00:00 > 00:00:00 > 00:00:00 > 01:00:00 > 01:00:00 > 01:00:00 > 02:00:00 > 02:00:00 > 03:00:00 > 03:00:00 > 04:00:00 > 04:00:00 > <null> > <null> > <null> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1766) EDS ODBC query on a namespace ending in 'e' fails

by Steven Hawkins (Closed) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1766?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1766. --------------------------------- > EDS ODBC query on a namespace ending in 'e' fails > ------------------------------------------------- > > Key: TEIID-1766 > URL: https://issues.jboss.org/browse/TEIID-1766 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Attachments: Testing.vdb > > > The attached testing vdb contains the following namespaces: > LOOKHERE TestPG LOOKAGAIN > If you run the following query via ODBC (JDBC works ): > select nspname from pg_catalog.pg_namespace where nspname = 'LOOKHERE' > It returns zero rows, but if you run the same query with 'LOOKAGAIN' in your criteria you get the one row, It seems that any namespace ending in an E doesn't match via ODBC. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1821) subqueries used in xmltable coulmn defaults are not resolved

by Steven Hawkins (Created) (JIRA)

subqueries used in xmltable coulmn defaults are not resolved ------------------------------------------------------------ Key: TEIID-1821 URL: https://issues.jboss.org/browse/TEIID-1821 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 7.6 The subqueries should be resolved and then fail validation. Currently they will produce a low level exception. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
2
0 / 0

[JBoss JIRA] (TEIID-1775) Ingres as source - WHERE CLAUSE is not returning expected results in some cases

by Steven Hawkins (Closed) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1775?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1775. --------------------------------- > Ingres as source - WHERE CLAUSE is not returning expected results in some cases > ------------------------------------------------------------------------------- > > Key: TEIID-1775 > URL: https://issues.jboss.org/browse/TEIID-1775 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 7.4.1 > Reporter: Warren Gibson > Assignee: Steven Hawkins > > EDS Query Testing is getting unexpected results on 24 queries involving WHERE CLAUSE. A few examples queries are given below: > SELECT BQT1.SmallA.TimeValue FROM BQT1.SmallA WHERE BQT1.SmallA.TimeValue > '17:00:00' ORDER BY TimeValue (Expected 11 records but received 23) > SELECT INTKEY, FLOATNUM FROM BQT1.SmallA WHERE RIGHT(FLOATNUM, 1) <> 0 ORDER BY INTKEY (Expected 43 records but received only 0) > SELECT BQT1.SmallA.StringKey, BQT2.SmallB.FloatNum FROM BQT1.SmallA, BQT2.SmallB WHERE BQT1.SmallA.StringKey = convert(BQT2.SmallB.FloatNum, string) AND BQT1.SmallA.IntKey >= 0 AND BQT2.SmallB.IntKey >= 0 ORDER BY BQT1.SmallA.StringKey (Expected 25 records but received only 0) > SELECT IntKey, TimeValue FROM (SELECT IntKey, TimeValue FROM BQT2.SmallA WHERE IntKey > 5) AS x WHERE TimeValue >= '17:00:00' ( Expected 13 records but received 20) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1803) VDB deployment in EDS can be extremely slow based upon indexing needs

by Johnathon Lee (Created) (JIRA)

VDB deployment in EDS can be extremely slow based upon indexing needs --------------------------------------------------------------------- Key: TEIID-1803 URL: https://issues.jboss.org/browse/TEIID-1803 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.4, 7.3, 7.2, 7.1.1 Environment: JBoss Enterprise Data Services Platform 5.1.0 Reporter: Johnathon Lee Assignee: Steven Hawkins Problem: The index metadata loading logic is not well optimized. In short, each time a call to IndexMetadataFactory.queryIndex is made the blocks are fully scanned. For small VDBs there isn't much of an issue because of the block caching logic, but during a vdb deploy we could be constantly re-reading data from the files. Possible solution: The IndexMetadataFactory loading strategy should be made aware of the index file per schema strategy so that scans can be made per schema rather than against all index files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
3
0 / 0

[JBoss JIRA] (TEIID-1782) Internal materialized views are not refreshed on both nodes in a Single, Non-Multihomed, Server

by Paul Nittel (Created) (JIRA)

Internal materialized views are not refreshed on both nodes in a Single, Non-Multihomed, Server ----------------------------------------------------------------------------------------------- Key: TEIID-1782 URL: https://issues.jboss.org/browse/TEIID-1782 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4.1 Environment: Fedora 14 Reporter: Paul Nittel Assignee: Steven Hawkins Attachments: PartsSourceA-ds.xml, PartsSourceB-ds.xml I have a cluster which is configured as a two-node single, non-multihomed, server. On each node (deployed as "Production" and named "node1" and "node2") I have deployed identical datasources and VDB. Shouldn't Materialized View management take place on all nodes in a cluster? The servers are started using: nohup ./run.sh -c node1 -g EDSPartition -b IPaddress -u 239.255.100.100 -Djboss.Domain=EDS -Djboss.jvmRoute="node1" -Djboss.messaging.ServerPeerID=1 -Djboss.service.binding.set=ports-default &>node1.out & nohup ./run.sh -c node2 -g EDSPartition -b IPaddress -u 239.255.100.100 -Djboss.Domain=EDS -Djboss.jvmRoute="node2" -Djboss.messaging.ServerPeerID=2 -Djboss.service.binding.set=ports-01 &>node2.out & I connect to the VDB using the following URL: mm://IPaddress:31000,IPaddress:31100 Querying the IMV table (PartsVirtual.SupplierInfo) loads one of the nodes, but not both. I can refresh both nodes by CALLing SYSADMIN.refreshMatView on each node in the cluster. Additionally, the transformation being queried contains a TTL of 30 seconds which never appears to expire. (It works as expected in a non-clustered environment.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

7
14
0 / 0

[JBoss JIRA] (TEIID-194) LDAP Connector should be deterministic about what value is returned when an attribute is multi-valued

by Steven Hawkins (Closed) (JIRA)

[ https://issues.jboss.org/browse/TEIID-194?page=com.atlassian.jira.plugin.... ] Steven Hawkins closed TEIID-194. -------------------------------- > LDAP Connector should be deterministic about what value is returned when an attribute is multi-valued > ----------------------------------------------------------------------------------------------------- > > Key: TEIID-194 > URL: https://issues.jboss.org/browse/TEIID-194 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 9.x > Reporter: Michael Walker > Priority: Minor > > The LDAP connector returns only one result for a multi-valued attribute. It does not make any attempt to return the same value in a deterministic way, but should do so. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-139) Enhancement: Language support for transactions

by Steven Hawkins (Closed) (JIRA)

[ https://issues.jboss.org/browse/TEIID-139?page=com.atlassian.jira.plugin.... ] Steven Hawkins closed TEIID-139. -------------------------------- > Enhancement: Language support for transactions > ---------------------------------------------- > > Key: TEIID-139 > URL: https://issues.jboss.org/browse/TEIID-139 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.0 > Reporter: Steven Hawkins > Priority: Optional > Fix For: 7.6 > > > Defect Tracker #20222: Supporting a limited transaction syntax, possibly similar to http://dev.mysql.com/doc/refman/4.1/en/commit.html, would allow the writers of virtual stored procedures to have declarative transaction handling rather than being forced to use the same transaction settings for all procedures based upon connection properties. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2011