All Apps and Add-ons

Splunk DB Connect character encoding problem

nembela
Path Finder

Hi,

 

I found a problem in Splunk DB connect when I tried to add a new input.

I can add new connections and the current inputs are working.

But when I try to add new input or try to use the “SQL Explorer” after choosing connection I get a “Cannot get schemas“ error message.

In the _internal index I found this error message: „Unable to get schemas metadata java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath): EE8ISO8859P2”

After this I updated DB Connect and the Oracle JDBC drivers but it did not help.

I consulted our DB admins. As it turned out these DBs really differ when it comes to character encoding (EE8ISO8859P2 vs. UTF8).

Of course the orai18n.jar file is there with the driver.

I found this in the documentation: https://docs.splunk.com/Documentation/DBX/3.14.1/DeployDBX/Troubleshooting#Unicode_decode_errors

"Splunk DB Connect requires you to set up your database connection to return results encoded in UTF-8. Consult your database vendor's documentation for instructions about how to do this."

Is it possible that DB Connect can only handle Oracle DB with UTF-8 encoding?

 

Thanks,

László

 

Labels (1)
0 Karma
Get Updates on the Splunk Community!

New This Month - Splunk Observability updates and improvements for faster ...

What’s New? This month, we’re delivering several enhancements across Splunk Observability Cloud for faster and ...

What's New in Splunk Cloud Platform 9.3.2411?

Hey Splunky People! We are excited to share the latest updates in Splunk Cloud Platform 9.3.2411. This release ...

Buttercup Games: Further Dashboarding Techniques (Part 6)

This series of blogs assumes you have already completed the Splunk Enterprise Search Tutorial as it uses the ...