Comment 1 Brian Fitzpatrick 2011-07-15 09:37:02 EDT

Hey Linda, since nothing else has changed in the core connectivity except for the OSGi tweaks you made for Indigo, I'm guessing this might be yours. It may have something to do with Oracle needing to change the enablement plug-ins they host themselves vs. what's in DTP?

Comment 2 Linda Chan 2011-07-15 17:47:06 EDT

I don't think the NPE has anything to do with my previous changes.
The stack trace points to the following code snippet, which is not related and could have more robust handling.  It looks like the driver template referenced by a driver instance no longer exists.  Perhaps the driver definitions are out of sync with the profiles in the user environment.  

  DriverInstance[] testDI = DriverManager.getInstance().getDriverInstancesByName(driverName);
  if (testDI != null) {
        // we found the driver, so we're ok to continue
	for (int index = 0; index < testDI.length; index++){
	     if (testDI[index].getTemplate().getId().equalsIgnoreCase(driverTypeID)) { // line 643
	       // the driver with the same name happens to have the same template ID, so we should be ok
	       xistingDriverHasName = true;
	      }
	}
   }

Comment 3 Brian Fitzpatrick 2011-07-18 17:33:14 EDT

Carsten - are you using the Oracle plug-ins that come with DTP or the ones that come from Oracle?

Comment 4 Carsten Nikiel 2011-07-28 03:19:32 EDT

I WAS using the DTP from Oracle, but since you mentioned it I uninstalled it.
NOW it works perfectly, but I miss some of the functionality from the OEPE.
Like the execution plan in graphical form (or even the textual form)

But at least without OEPE I do not have to type in the connection details each time I start eclipse.

(In reply to comment #3)
> Carsten - are you using the Oracle plug-ins that come with DTP or the ones that
> come from Oracle?

Comment 5 Brian Fitzpatrick 2011-07-28 09:20:50 EDT

(In reply to comment #4)
> I WAS using the DTP from Oracle, but since you mentioned it I uninstalled it.
> NOW it works perfectly, but I miss some of the functionality from the OEPE.
> Like the execution plan in graphical form (or even the textual form)
> 
> But at least without OEPE I do not have to type in the connection details each
> time I start eclipse.

Thanks Carsten - that gives me somewhere to start. I'm unable to reproduce it locally and suspected I was missing something. I'll see if I can get this licked for the first maintenance release.

Comment 6 Matthew Buckett 2013-03-05 06:25:18 EST

I'm seeing this on Juno SR2 importing connection profiles generated from Indigo.

Comment 7 Matthew Buckett 2013-03-05 06:33:02 EST

Created attachment 227928 [details]
connection specification that is failing to import.

connections.dat is an edited attachement that is failing to import for me on Juno SR2.

Comment 8 Matthew Buckett 2013-03-05 06:40:15 EST

Created attachment 227929 [details]
stack trace from juno SR when import fails

Stack trace from: Build id: 20130225-0426 with DTP version 1.10.2.v201209181447

Comment 9 Matthew Buckett 2013-03-05 06:49:51 EST

My problem was that I had the Data Toole Platform Extender SDK installed but not the Data Tool Platform Enablement Extender SDK. Installing the Extender allowed the import of the connection profiles to work without a problem.

I still think it stands as a bug because you should get a better error message.

Comment 10 Nobody - feel free to take it 2015-02-16 02:29:57 EST

SPAM comment removed