Why does DB Connect 2 get "not supported type" trying to retrieve an XMLType Column while DB Connect 1 retrieves it successfully?

[jamiemccallion]

This is an interesting one...

Splunk DB Connect 1 connects to the Oracle 11g db and retrieves an XMLType column just fine when queried like so:

SELECT FIELD1,X.XML_DOCUMENT.GETCLOBVAL() as XML_DOC,FIELD2,FIELD3,FIELD4,FIELD5 FROM Data.table X

Splunk DB Connect 2 - same driver, same database, same credentials, same command, gets
"## Not Supported Type ##" for the XML_DOC field, but the others come back fine.

ojdbc6.jar in both cases.
DBX v1 is using built-in OS Java version (1.7.0, IBM)
DBX v2 is using a local Java (1.8.0_45, Oracle)

What do you think? Java version problem? DBXv2 code problem?
Has anyone else encountered this?

Thanks for any assistance!

[jamiemccallion · Accepted solution]

Sorry, should have replied a couple of weeks ago.
I tested some more, and identified that it wasn't a Java problem (using a DBXv1 release supports Java 8).

Case was raised with support, and a bug identified in 2.0.x with the way that it handles some field-types in the response from the database.

Support advised that it will be resolved in a future release of DBX2; workaround is to continue using DBXv1 for those specific problem field-types in the interim.

[nekbote]

Well we upgraded from DBXv1 to DBXv2 as we were losing records while using dump with DBXv1 ...purpose of upgrading to DBXv2 has failed [atleast for the moment] due to "## Not Supported Type ##".

Isn't there any work around at all with DBXv2? Any idea when will the future release be?

Any response will be appreciated.

[jcoates_splunk]

Hi,

I think that this will be about Java versions... We don't support IBM Java for DBX 1 or 2, by the way.

• DB Connect version 1.1.7, we support Oracle Java 7
• DB Connect version 1.2.0, we support Oracle Java 8
• DB Connect version 1.2.1, we support Oracle Java 7 or 8
• DB Connect version 2.*, we support Oracle Java 8

If it works with 1.2.1, Oracle Java 8, but then doesn't work with DB Connect 2 and the same environment, then it's a DB Connect bug and needs a support case.

[amielke]

Has anyone found a solution?