January 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1572) Unable to import over 5000 Tables from Oracle schema due to maximum open cursors exceeded

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1572?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1572: ----------------------------------- Fix Version/s: 8.1 > Unable to import over 5000 Tables from Oracle schema due to maximum open cursors exceeded > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-1572 > URL: https://issues.jboss.org/browse/TEIIDDES-1572 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.1 > > > Importing from oracle data source produced the following error: > !STACK 0 > java.sql.SQLException: ORA-01000: maximum open cursors exceeded > at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439) > at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395) > at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802) > at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436) > at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186) > at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521) > at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:194) > at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:853) > at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1145) > at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1267) > at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1469) > at oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:389) > at oracle.jdbc.OracleDatabaseMetaData.getCatalogs(OracleDatabaseMetaData.java:3120) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.getCatalogs(RelationalModelProcessorImpl.java:2529) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.computeNameInSource(RelationalModelProcessorImpl.java:2616) > at com.metamatrix.modeler.jdbc.relational.impl.custom.OracleModelProcessor.computeNameInSource(OracleModelProcessor.java:263) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.setNameAndNameInSource(RelationalModelProcessorImpl.java:2469) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.setNameAndNameInSource(RelationalModelProcessorImpl.java:2422) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.createNewObject(RelationalModelProcessorImpl.java:1104) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.performExecute(RelationalModelProcessorImpl.java:824) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl$1.run(RelationalModelProcessorImpl.java:329) > at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:550) > at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:593) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:336) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:312) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.execute(RelationalModelProcessorImpl.java:302) > at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportWizard.runFinish(JdbcImportWizard.java:716) > at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportWizard$1.run(JdbcImportWizard.java:275) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > !SUBENTRY 1 org.teiid.designer.compare 0 50010 2013-01-30 09:43:41.558 > !MESSAGE Completed difference analysis -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1572) Unable to import over 5000 Tables from Oracle schema due to maximum open cursors exceeded

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1572?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1572: ---------------------------------------- A few spots in our code where ResultSet and Statement objects were being obtained from JDBC methods that didn't close them. > Unable to import over 5000 Tables from Oracle schema due to maximum open cursors exceeded > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-1572 > URL: https://issues.jboss.org/browse/TEIIDDES-1572 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.1 > > > Importing from oracle data source produced the following error: > !STACK 0 > java.sql.SQLException: ORA-01000: maximum open cursors exceeded > at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439) > at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395) > at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802) > at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436) > at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186) > at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521) > at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:194) > at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:853) > at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1145) > at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1267) > at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1469) > at oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:389) > at oracle.jdbc.OracleDatabaseMetaData.getCatalogs(OracleDatabaseMetaData.java:3120) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.getCatalogs(RelationalModelProcessorImpl.java:2529) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.computeNameInSource(RelationalModelProcessorImpl.java:2616) > at com.metamatrix.modeler.jdbc.relational.impl.custom.OracleModelProcessor.computeNameInSource(OracleModelProcessor.java:263) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.setNameAndNameInSource(RelationalModelProcessorImpl.java:2469) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.setNameAndNameInSource(RelationalModelProcessorImpl.java:2422) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.createNewObject(RelationalModelProcessorImpl.java:1104) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.performExecute(RelationalModelProcessorImpl.java:824) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl$1.run(RelationalModelProcessorImpl.java:329) > at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:550) > at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:593) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:336) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:312) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.execute(RelationalModelProcessorImpl.java:302) > at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportWizard.runFinish(JdbcImportWizard.java:716) > at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportWizard$1.run(JdbcImportWizard.java:275) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > !SUBENTRY 1 org.teiid.designer.compare 0 50010 2013-01-30 09:43:41.558 > !MESSAGE Completed difference analysis -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1572) Unable to import over 5000 Tables from Oracle schema due to maximum open cursors exceeded

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-1572: ------------------------------------- Summary: Unable to import over 5000 Tables from Oracle schema due to maximum open cursors exceeded Key: TEIIDDES-1572 URL: https://issues.jboss.org/browse/TEIIDDES-1572 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.7 Reporter: Van Halbert Assignee: Barry LaFond Importing from oracle data source produced the following error: !STACK 0 java.sql.SQLException: ORA-01000: maximum open cursors exceeded at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395) at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521) at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:194) at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:853) at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1145) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1267) at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1469) at oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:389) at oracle.jdbc.OracleDatabaseMetaData.getCatalogs(OracleDatabaseMetaData.java:3120) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.getCatalogs(RelationalModelProcessorImpl.java:2529) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.computeNameInSource(RelationalModelProcessorImpl.java:2616) at com.metamatrix.modeler.jdbc.relational.impl.custom.OracleModelProcessor.computeNameInSource(OracleModelProcessor.java:263) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.setNameAndNameInSource(RelationalModelProcessorImpl.java:2469) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.setNameAndNameInSource(RelationalModelProcessorImpl.java:2422) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.createNewObject(RelationalModelProcessorImpl.java:1104) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.performExecute(RelationalModelProcessorImpl.java:824) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl$1.run(RelationalModelProcessorImpl.java:329) at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:550) at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:593) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:336) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:312) at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.execute(RelationalModelProcessorImpl.java:302) at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportWizard.runFinish(JdbcImportWizard.java:716) at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportWizard$1.run(JdbcImportWizard.java:275) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) !SUBENTRY 1 org.teiid.designer.compare 0 50010 2013-01-30 09:43:41.558 !MESSAGE Completed difference analysis -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1538) Cannot change HEDER option in TEXTTABLE() function by Flat File import wizard

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1538?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1538: ----------------------------------- Fix Version/s: 8.1 > Cannot change HEDER option in TEXTTABLE() function by Flat File import wizard > ----------------------------------------------------------------------------- > > Key: TEIIDDES-1538 > URL: https://issues.jboss.org/browse/TEIIDDES-1538 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.7.1, 7.8 > Environment: JBDS 5.0.1 > Reporter: Eiichi Nagai > Assignee: Barry LaFond > Fix For: 8.1 > > Attachments: FlatFileDelimitedColumnsParserSetting.png > > > There is a setup of the Format Options configuration in Flat File import wizard. > A HEDER option in TEXTTABLE() function is contained in Generated SQL Statement even if it disables the 'Column names in header' check box. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1545) "WSDL to Relational" importer fields for Source and View Model Definition Name enter backwards in Windows

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1545?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1545: ----------------------------------- Assignee: Dan Florian > "WSDL to Relational" importer fields for Source and View Model Definition Name enter backwards in Windows > --------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1545 > URL: https://issues.jboss.org/browse/TEIIDDES-1545 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.7 > Environment: Windows 7 64 bit > JBDS 5.0 > Teiid Designer Plugin version 7.7.2.v20121025-2138-H6-GA-SOA > Reporter: Debbie Steigner > Assignee: Dan Florian > > I have only found this issue on Windows JBDS installation. Import > "WSDL File or URL >> Source and View Model" proceed thru the wizard until you reach the "Models Definition" page, do not take the default names for Source. Try entering a name, the cursor returns to column 1 after each letter so hello becomes olleh. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1545) "WSDL to Relational" importer fields for Source and View Model Definition Name enter backwards in Windows

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1545?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1545: ----------------------------------- Fix Version/s: 8.1 > "WSDL to Relational" importer fields for Source and View Model Definition Name enter backwards in Windows > --------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1545 > URL: https://issues.jboss.org/browse/TEIIDDES-1545 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.7 > Environment: Windows 7 64 bit > JBDS 5.0 > Teiid Designer Plugin version 7.7.2.v20121025-2138-H6-GA-SOA > Reporter: Debbie Steigner > Assignee: Dan Florian > Fix For: 8.1 > > > I have only found this issue on Windows JBDS installation. Import > "WSDL File or URL >> Source and View Model" proceed thru the wizard until you reach the "Models Definition" page, do not take the default names for Source. Try entering a name, the cursor returns to column 1 after each letter so hello becomes olleh. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1538) Cannot change HEDER option in TEXTTABLE() function by Flat File import wizard

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1538?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1538: ----------------------------------- Assignee: Barry LaFond > Cannot change HEDER option in TEXTTABLE() function by Flat File import wizard > ----------------------------------------------------------------------------- > > Key: TEIIDDES-1538 > URL: https://issues.jboss.org/browse/TEIIDDES-1538 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.7.1, 7.8 > Environment: JBDS 5.0.1 > Reporter: Eiichi Nagai > Assignee: Barry LaFond > Attachments: FlatFileDelimitedColumnsParserSetting.png > > > There is a setup of the Format Options configuration in Flat File import wizard. > A HEDER option in TEXTTABLE() function is contained in Generated SQL Statement even if it disables the 'Column names in header' check box. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1548) Add GUI handling for permission conditions

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1548?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1548: ---------------------------------------- This is possible, but would require new level of validation within a VDB. Currently, validation is "per model" and utilizes existing model validation. Validating a "SQL Condition" against a resource will require a different validation OR required injecting additional/external validation during the model validation > Add GUI handling for permission conditions > ------------------------------------------ > > Key: TEIIDDES-1548 > URL: https://issues.jboss.org/browse/TEIIDDES-1548 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Steven Hawkins > > A common request is to implement row based security. Teiid has added the ability to define a permission condition for this purpose: > <permission> > <resource-name>...</resource-name> > <condition>sql</condition> > ... > </permission> > The sql should resolve against the resource specified, ideally designer would check that as well. > See TEIID-2311 and the reference for how these conditions are applied. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1557) Add Greenplum importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1557?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1557: ---------------------------------------- Auto-recognizing Greenplum DB is possible, but only if there is a connection profile contributed to Data Tools that defines a "vendor ID". > Add Greenplum importer > ---------------------- > > Key: TEIIDDES-1557 > URL: https://issues.jboss.org/browse/TEIIDDES-1557 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 8.0 > Reporter: Van Halbert > Fix For: Future > > > Add support for importing from a Greenplum data source. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1446) Usability: Need to clean up how a user points a source model at a different database

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1446?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1446. ------------------------------------ Assignee: Barry LaFond Resolution: Cannot Reproduce Bug Tested today with 8.1 code and walked through in debug. Changing connection profile results in deletion of the source model's preview VDB and data source. Subsequent preview returned data from the changed data source. > Usability: Need to clean up how a user points a source model at a different database > ------------------------------------------------------------------------------------ > > Key: TEIIDDES-1446 > URL: https://issues.jboss.org/browse/TEIIDDES-1446 > Project: Teiid Designer > Issue Type: Bug > Components: Usability > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.1 > > > Was trying to redirect the source models at a different database. I thought it was first obvious to change the Data Source properties for each source model. But that had no effect. Then Barry indicated that I had to use the "Set Connection Profile" option. I then set the connection profile to use. But I had to close the project and reopen so that the PREVIEW... artifacts on the server were removed and got reloaded upon opening of the project. > I think from a usability standpoint, this needs to be changed. Especially since Designer depends on the connection profile so much, keeping and allowing editing of its own data source properties makes it confusing. -- 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, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2013