[bozman42]

I’m trying to use the DB explorer to connect an IBM UniVerse database, but I’m having some troubles. I’ve created a small test program that allows me to do a simple select, but when trying to connect via the DB explorer I get an error and the following stack trace in .metadata/.log:

!ENTRY com.genuitec.eclipse.sqlexplorer 4 4 2007-09-11 13:33:10.535
!MESSAGE Error while performing database login with the Universe driver
!STACK 0
java.lang.NullPointerException
at com.genuitec.eclipse.sqlexplorer.actions.OpenPasswordConnectDialogAction.perfomLoginAndRetrieval(OpenPasswordConnectDialogAction.java:122)
at com.genuitec.eclipse.sqlexplorer.actions.OpenPasswordConnectDialogAction.run(OpenPasswordConnectDialogAction.java:82)
at com.genuitec.eclipse.sqlexplorer.actions.NewConnection.run(NewConnection.java:70)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
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:504)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
at org.eclipse.equinox.launcher.Main.run(Main.java:1169)

[bozman42]

Here is my system info:

*** Date:
Tuesday, September 11, 2007 2:35:38 PM CDT

** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.6.0

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 6.0.0 GA
Build id: 6.0.0-GA-200708

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 6.0.0 GA
Build id: 6.0.0-GA-200708

Eclipse Project SDK

Version: 3.3.0.v20070607-7M7J-BIolz-OcxWxvWAPSfLPqevO
Build id: I20070625-1500

Eclipse Platform

Version: 3.3.0.v20070612-_19UEkLEzwsdF9jSqQ-G
Build id: I20070625-1500

Eclipse Plug-in Development Environment

Version: 3.3.0.v20070607-7N7M-DUUEF6Ez0H46IcCC
Build id: I20070625-1500

Eclipse RCP

Version: 3.3.0.v20070607-8y8eE8NEbsN3X_fjWS8HPNG
Build id: I20070625-1500

Eclipse Java Development Tools

Version: 3.3.0.v20070606-0010-7o7jCHEFpPoqQYvnXqejeR
Build id: I20070625-1500

Eclipse Graphical Editing Framework

Version: 3.3.0.v20070620
Build id: 20070620-1021

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\sw\tt\BD-TOOLS\eclipse\sdk-3.3\eclipse\eclipse.exe
-name
Eclipse
–launcher.library
C:\sw\tt\BD-TOOLS\eclipse\sdk-3.3\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.0.v20070523\eclipse_1017a.dll
-startup
C:\sw\tt\BD-TOOLS\eclipse\sdk-3.3\eclipse\plugins\org.eclipse.equinox.launcher_1.0.0.v20070606.jar
-data
C:\my\sb\eclipse\nsa-apps\nsa-uvh
-launcher
C:\sw\tt\BD-TOOLS\eclipse\sdk-3.3\eclipse\eclipse.exe
-product
com.genuitec.myeclipse.product.ide
-vm
C:\sw\tt\java\jre1.6.0\bin\client\jvm.dll

[Riyad Kalla]

bozman,
Unfortunately we don’t have that DB locally to be able to test what is going on, but since the DB Explorer is written against the JDBC API, 95% of the problems we see with DB’s is because of bugs or problems with the JDBC driver.

Just make sure you are using the latest JDBC driver with the DB Explorer and that’s the best we can do at the moment as far as troubleshooting.

[bozman42]

@support-rkalla wrote:

bozman,
Unfortunately we don’t have that DB locally to be able to test what is going on, but since the DB Explorer is written against the JDBC API, 95% of the problems we see with DB’s is because of bugs or problems with the JDBC driver.

Just make sure you are using the latest JDBC driver with the DB Explorer and that’s the best we can do at the moment as far as troubleshooting.

Thank you for the response, I already had concluded that there might be an issue with the driver, so I’ve gone in search of updated one with no luck at all, I’ve searched IBM’s website up and down without any luck.

[Author]

Posts