Are We Related?

Tools
Tools covers the tools and utilities you use to work with Teradata and its supporting ecosystem. You'll find information on everything from the Teradata Eclipse plug-in to load/extract tools.
Teradata Employee

Re: Are We Related?

@asamoal, It looks like GlassFish 3.x now uses the service name with the word "Service" appended to the name. To workaround this issue, use the tomcat version of the Teradata MetaData WAR, in the /tc directory, instead of the GlassFish WAR (in /gf).
Highlighted
Enthusiast

Re: Are We Related?

I can see the system loaded as that defined in mds when we use the Test user button. but upon checking for interdependence on object we get the following error
com.teradata.datatools.dependencies.TeradataInterdependenciesException: Could not log on user
at com.teradata.datatools.dependencies.mdsimpl.TeradataInterdependencies.(TeradataInterdependencies.java:134)
at com.teradata.datatools.dependencies.TeradataInterdependencies.getTeradataInterdependencies(TeradataInterdependencies.java:33)
at com.teradata.datatools.dependencies.ui.ShowInterdependencies.showInInterdepencencyBrowser(ShowInterdependencies.java:186)
at com.teradata.datatools.dependencies.ui.ShowInterdependencies.run(ShowInterdependencies.java:134)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
Caused by: com.teradata.datatools.mdswsclient.TeradataMdsWsClientException: Could not get object keys for objectType DatabaseSystem
at com.teradata.datatools.mdswsclient.impl.TeradataMdsWsClient.getObjectKeys(TeradataMdsWsClient.java:297)
at com.teradata.datatools.mdswsclient.impl.TeradataMdsWsClient.getObjectKeys(TeradataMdsWsClient.java:271)
at com.teradata.datatools.mdswsclient.impl.TeradataMdsWsClient.(TeradataMdsWsClient.java:104)
at com.teradata.datatools.mdswsclient.TeradataMdsWsClient.getTeradataMdsWsClient(TeradataMdsWsClient.java:43)
at com.teradata.datatools.dependencies.mdsimpl.TeradataInterdependencies.(TeradataInterdependencies.java:122)
... 31 more
Caused by: com.teradata.mdsws.access.MetaException_Exception: META_E_UNKNOWN_USER
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown Source)
at $Proxy32.getClassObjectKeys(Unknown Source)
at com.teradata.datatools.mdswsclient.impl.TeradataMdsWsClient.getObjectKeys(TeradataMdsWsClient.java:287)
... 35 more

Teradata Employee

Re: Are We Related?

@ak93, Have you set the MDS log on information in the Dependencies Preferences page?
Enthusiast

Re: Are We Related?

yes i have set the MDS login to metasu and that is working when we test the user in the preferences pane (it display the systme name correctly) . however when checking the interdependencies it fails with the error message posted in my previous comment
Teradata Employee

Re: Are We Related?

@ak93, That is odd since the exception indicates an UNKNOWN_USER. Can you turn MDS logging on and retrieve the MDS Log and send (please open a new topic on the Teradata Studio forum to attach your log file).

To get the MDS Log: Set logging to “All” from the MetaMgr “Logon” dialog, click the “Configure” button, and from the MDS Configuration dialog that comes up, select the “Logging” tab. In the left panel (“Logging level”) select the “All” radio button and hit Apply. From the Teradata Studio Dependencies Preference Page, click the Test User button. Also recreate the problem and then send the log file to us (the file name is in the box on this dialog).
Enthusiast

Re: Are We Related?