[JBoss JIRA] (TEIIDDES-1588) Cannot import datatypes from csv file
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1588?page=com.atlassian.jira.plu... ]
Andrej Podhradsky updated TEIIDDES-1588:
----------------------------------------
Attachment: error.txt
> Cannot import datatypes from csv file
> -------------------------------------
>
> Key: TEIIDDES-1588
> URL: https://issues.jboss.org/browse/TEIIDDES-1588
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.0
> Reporter: Andrej Podhradsky
> Attachments: error.txt, relationalDatatype.csv, relationalDatatype2.csv
>
>
> Cannot import datatypes from csv file which is created from the wizard suggestion (relationalDatatypes.csv).
> After importing the following error occurs
> <Missing message for key "ImportDatatypesMainPage.importError" in: org.teiid.designer.xsd.ui.i18n>
> and error which is can be found in the attachment.
> Moreover, the following warning also occurs
> Could not parse the following row: TYPETAG,Name,Description,BaseType,Length,MinLength,MaxLength,MinBound,MinInclusive,MaxBound,MaxInclusive,TotalDigits,Fraction Digits.
> Note that I also tried to import datatypes without the first line (relationalDatatypes2.csv) but the same error occurs (without the warning).
--
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
13 years, 2 months
[JBoss JIRA] (TEIIDDES-1588) Cannot import datatypes from csv file
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created TEIIDDES-1588:
-------------------------------------------
Summary: Cannot import datatypes from csv file
Key: TEIIDDES-1588
URL: https://issues.jboss.org/browse/TEIIDDES-1588
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 8.0
Reporter: Andrej Podhradsky
Cannot import datatypes from csv file which is created from the wizard suggestion (relationalDatatypes.csv).
After importing the following error occurs
<Missing message for key "ImportDatatypesMainPage.importError" in: org.teiid.designer.xsd.ui.i18n>
and error which is can be found in the attachment.
Moreover, the following warning also occurs
Could not parse the following row: TYPETAG,Name,Description,BaseType,Length,MinLength,MaxLength,MinBound,MinInclusive,MaxBound,MaxInclusive,TotalDigits,Fraction Digits.
Note that I also tried to import datatypes without the first line (relationalDatatypes2.csv) but the same error occurs (without the warning).
--
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
13 years, 2 months
[JBoss JIRA] (TEIIDDES-1577) Changing connection URL for JDBC driver has no effect
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1577?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-1577:
----------------------------------------
Once created the Driver profile can not be changed. If you want to edit the Connection profile you created, then click the "edit" on "import Database via JDBC" dialog box.
> Changing connection URL for JDBC driver has no effect
> -----------------------------------------------------
>
> Key: TEIIDDES-1577
> URL: https://issues.jboss.org/browse/TEIIDDES-1577
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Tom Johnston
>
> Changing Connection URL under Properties Tab for Edit Driver Definitions does not have any impact when using the driver.
> I.E. When specifying a new connection profile the Connection URL (shaded, unchangeable here) does NOT reflect the aforementioned property.
> Use Case: I'm trying to create a new driver entry using Oracles OCI connectivity capability thus requiring a change in the connection url to (jdbc:oracle:oci:@<database_string> , for example)
--
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
13 years, 2 months
[JBoss JIRA] (TEIIDDES-1577) Changing connection URL for JDBC driver has no effect
by Tom Johnston (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1577?page=com.atlassian.jira.plu... ]
Tom Johnston commented on TEIIDDES-1577:
----------------------------------------
Ramesh, thank you very much for the workaround. I have confirmed that the creation of a new connection profile following your instructions does indeed work. Editing an existing one is still not possible as I originally reported.
> Changing connection URL for JDBC driver has no effect
> -----------------------------------------------------
>
> Key: TEIIDDES-1577
> URL: https://issues.jboss.org/browse/TEIIDDES-1577
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Tom Johnston
>
> Changing Connection URL under Properties Tab for Edit Driver Definitions does not have any impact when using the driver.
> I.E. When specifying a new connection profile the Connection URL (shaded, unchangeable here) does NOT reflect the aforementioned property.
> Use Case: I'm trying to create a new driver entry using Oracles OCI connectivity capability thus requiring a change in the connection url to (jdbc:oracle:oci:@<database_string> , for example)
--
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
13 years, 2 months
[JBoss JIRA] (TEIIDDES-1216) New View Table Wizard
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1216?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1216:
-----------------------------------
Fix Version/s: Future
(was: 8.1)
This wizard would be nice, but the new work in TEIIDDES-1523 gets us closer to an answer for creating a more complete virtual table up front. Pushing to future to re-evaluate.
> New View Table Wizard
> ---------------------
>
> Key: TEIIDDES-1216
> URL: https://issues.jboss.org/browse/TEIIDDES-1216
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling, Transformations
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: Future
>
> Attachments: Create View Table Wizard.bmml, Create View Table Wizard.png, CreateViewTableWizard.png, View Easy Edit Mockup.bmml, View Easy Edit Mockup.bmml, View Easy Edit Mockup.png
>
>
> In our push to improve usability, a new "Create View Table" wizard could provide a new means to create views using the Join or Union concept.
> Result of the wizard would be a complete, valid SQL transformation that is reconciled, use "functions" in Symbol definition and include Criteria
--
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
13 years, 2 months
[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:
----------------------------------------
committed fixes to catch these spots and add close() calls to 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
13 years, 2 months
[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:
-----------------------------------
Assignee: Van Halbert (was: Barry LaFond)
> 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: Van Halbert
> 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
13 years, 2 months
[JBoss JIRA] (TEIIDDES-1010) Indexes are not qualified when imported with Teiid Designer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1010?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1010.
------------------------------------
Resolution: Done
Done
> Indexes are not qualified when imported with Teiid Designer
> -----------------------------------------------------------
>
> Key: TEIIDDES-1010
> URL: https://issues.jboss.org/browse/TEIIDDES-1010
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 7.4
> Reporter: Marc Shirley
> Assignee: Barry LaFond
> Fix For: 8.1
>
> Attachments: org.teiid.designer.jdbc.relational.patch
>
>
> Having multiple indexes with the same name (for example, 'PrimaryKey') imported results in a conflict or merging of the indexes. This generates messages complaining of an index referring to multiple tables in the Teiid Designer perspective. The indexes should be qualified in order to remain unique or generated as a child of the associated table in order to avoid these messages.
--
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
13 years, 2 months