[JBoss JIRA] (TEIIDDES-3060) Duplicate UUID on VDB generated from Teiid Designer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3060?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-3060:
-----------------------------------
Fix Version/s: 11.3
(was: 11.2)
> Duplicate UUID on VDB generated from Teiid Designer
> ---------------------------------------------------
>
> Key: TEIIDDES-3060
> URL: https://issues.jboss.org/browse/TEIIDDES-3060
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 9.1
> Reporter: Abraham Arellano Tavara
> Priority: Critical
> Fix For: 11.3
>
> Attachments: BoGeschVorgangLesenDataM.xmi, Negativmerkmal.xmi, PersonTyp.xmi, Regeldaten.xmi, RegeldatenFedView_lean.vdb, SvzEintragM.xmi, error_trace.txt, utilView.xmi
>
>
> The error of duplicated UUID is thrown when a VDB generated by the Teiid Designer is deployed. There are 2 return object from 2 different functions which have the same UUID.
> The exception is: (The full trace is attached "error_trace.txt")
> java.lang.AssertionError: duplicate uid object result
> In more detail the following views / functions have the same UUID:
> + SvzEintragM / dvkSvz_liesEintragAusSvz
> + BoGeschVorgangLesenDataM / dvkVorgang_liesVorgang
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2898) JDBC import wizard (update) stops after importing 1 database of 3
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2898?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2898:
-----------------------------------
Fix Version/s: Future
(was: 11.2)
> JDBC import wizard (update) stops after importing 1 database of 3
> -----------------------------------------------------------------
>
> Key: TEIIDDES-2898
> URL: https://issues.jboss.org/browse/TEIIDDES-2898
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 10.1
> Reporter: Bram Gadeyne
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: Future
>
>
> I'm trying to update an xmi file that contains tables from 3 databases on one server.
> Teiiddesigner is connected to the teiid server.
> Step 1: select connection + sybase metadata processor (using the jtds driver)
> Step 2: select table types SYSTEM TABLE, TABLE and VIEW
> Step 3: deselect 1 of the selected databases (AUDITARCHIVE), select 3 times dbo from required databases (Department, Patient, System)
> Step 4: Select model to update, deselect include cost statistics, deselect auto create data source. In second tab select "Use fully qualified Names"
> When I click next now the wizard starts to read the database. It indicates that it is reading table x of 13xx.
> It starts of with database Department. When it reaches 101 objects it stops. I think this is when it starts reading one of the other databases.
> Prior to the start of this reading process there is an exception stack trace in the logs. While reading the database there is however no indication of an error.
> The 101 objects are indicated as new and all other objects are indicated as removed (however most should be updates).
> This is the stack trace prior to clicking next after step 4. It mentions AUDITARCHIVE which I've deslected.
> !ENTRY org.teiid.designer.jdbc 2 0 2016-08-17 10:12:04.983
> !MESSAGE Unexpected exception while calling net.sourceforge.jtds.jdbc.JtdsDatabaseMetaData.getTableTypes() and processing results on DatabaseIZISprod
> !STACK 0
> java.sql.SQLException: Server user id 1227 is not a valid user in database 'AUDITARCHIVE'
> at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372)
> at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2988)
> at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2421)
> at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:671)
> at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:505)
> at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeQuery(JtdsPreparedStatement.java:1032)
> at net.sourceforge.jtds.jdbc.JtdsDatabaseMetaData.getTables(JtdsDatabaseMetaData.java:1836)
> at org.teiid.designer.jdbc.metadata.impl.JdbcTableTypeImpl.computeChildren(JdbcTableTypeImpl.java:58)
> at org.teiid.designer.jdbc.metadata.impl.JdbcNodeImpl.getChildren(JdbcNodeImpl.java:197)
> at org.teiid.designer.jdbc.ui.wizards.JdbcImportObjectsPage.updateCounts(JdbcImportObjectsPage.java:799)
> at org.teiid.designer.jdbc.ui.wizards.JdbcImportObjectsPage.updateCounts(JdbcImportObjectsPage.java:799)
> at org.teiid.designer.jdbc.ui.wizards.JdbcImportObjectsPage.updateCounts(JdbcImportObjectsPage.java:799)
> at org.teiid.designer.jdbc.ui.wizards.JdbcImportObjectsPage.validatePage(JdbcImportObjectsPage.java:821)
> at org.teiid.designer.jdbc.ui.wizards.JdbcImportObjectsPage.refresh(JdbcImportObjectsPage.java:555)
> at org.teiid.designer.jdbc.ui.wizards.JdbcImportObjectsPage.setVisible(JdbcImportObjectsPage.java:454)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1229)
> at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1208)
> at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1197)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1194)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:885)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:425)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4180)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3769)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:158)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160)
> at org.eclipse.ui.internal.actions.CommandAction.run(CommandAction.java:175)
> at org.eclipse.ui.actions.ImportResourcesAction.run(ImportResourcesAction.java:99)
> at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:170)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4180)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3769)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2608) Model editor blank after restarting JBDS
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2608?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2608:
-----------------------------------
Fix Version/s: Future
(was: 11.2)
> Model editor blank after restarting JBDS
> ----------------------------------------
>
> Key: TEIIDDES-2608
> URL: https://issues.jboss.org/browse/TEIIDDES-2608
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors, Patch Release
> Affects Versions: 9.0.3
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: Future
>
> Attachments: 2016-04-14 11.23.bmml, Screen Shot 2016-02-17 at 15.05.25.png, Selection_013.png, log
>
>
> After closing JBDS and starting again, the last opened model editor is blank.
> This might be related to TEIIDDES-2597.
> Eclipse log attached.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2689) LDAP dialogue too slow - loads a lot of data?
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2689?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2689:
-----------------------------------
Fix Version/s: Future
(was: 11.2)
> LDAP dialogue too slow - loads a lot of data?
> ---------------------------------------------
>
> Key: TEIIDDES-2689
> URL: https://issues.jboss.org/browse/TEIIDDES-2689
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Affects Versions: 9.0.4
> Environment: MAC OS
> Reporter: Matus Makovy
> Assignee: Paul Richardson
> Priority: Critical
> Fix For: Future
>
> Attachments: Screen Shot 2015-10-14 at 14.17.46.png
>
>
> I came across this when trying to verify TEIIDDES-2478.
> When you have a LDAP instance with big amount of entries (in the screenshot you can see that are 931 entries) in some part, it takes long to load all attributes. After clicking Next> on the page shown in screenshot (see attachment) JBDS freezes and doesn't respond for about 3 minutes. At least we should have some message that says, that TD is loading data from LDAP.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2953) Static VDB with JDG materialization has a warning after deploy
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2953?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-2953:
---------------------------------------
[~dsteigne] Are they using JDG 6 or 7?
> Static VDB with JDG materialization has a warning after deploy
> --------------------------------------------------------------
>
> Key: TEIIDDES-2953
> URL: https://issues.jboss.org/browse/TEIIDDES-2953
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 11.2
>
> Attachments: completeJDGproject2.zip
>
>
> I have a project with JDG materialization. When I want to deploy static VDB, server shows me error that:
> {code:java}
> 15:47:10,347 WARN [org.teiid.MATVIEWS] (Worker1_QueryProcessorQueue9) org.teiid.jdbc.TeiidSQLException: TEIID30168 Couldn't execute the dynamic SQL command "EXECUTE IMMEDIATE array_get(strings, index)" with the SQL statement "execute BookCacheSource.native('truncate cache')" due to: TEIID30357 BookCacheSource.native does not exist.
> {code}
> But when I deploy dynamic VDB, which is generated from that staticVDB, server doesn't shows any errors and materialization works fine.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2953) Static VDB with JDG materialization has a warning after deploy
by Debbie Steigner (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2953?page=com.atlassian.jira.plu... ]
Debbie Steigner reassigned TEIIDDES-2953:
-----------------------------------------
Assignee: Barry LaFond
> Static VDB with JDG materialization has a warning after deploy
> --------------------------------------------------------------
>
> Key: TEIIDDES-2953
> URL: https://issues.jboss.org/browse/TEIIDDES-2953
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 11.2
>
> Attachments: completeJDGproject2.zip
>
>
> I have a project with JDG materialization. When I want to deploy static VDB, server shows me error that:
> {code:java}
> 15:47:10,347 WARN [org.teiid.MATVIEWS] (Worker1_QueryProcessorQueue9) org.teiid.jdbc.TeiidSQLException: TEIID30168 Couldn't execute the dynamic SQL command "EXECUTE IMMEDIATE array_get(strings, index)" with the SQL statement "execute BookCacheSource.native('truncate cache')" due to: TEIID30357 BookCacheSource.native does not exist.
> {code}
> But when I deploy dynamic VDB, which is generated from that staticVDB, server doesn't shows any errors and materialization works fine.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months