Splunk® DB Connect

Release Notes

Acrobat logo Download manual as PDF

This documentation does not apply to the most recent version of Splunk® DB Connect. Click here for the latest version.
Acrobat logo Download topic as PDF

Release notes

Version 3.4.0 of Splunk DB Connect was released on August 19, 2020.

New and changed features

Version 3.4.0 of Splunk DB Connect contains the following new or changed features:

  • Support for Oracle version 19c.
  • DBX lookup memory tuning.
  • Support for AWS Oracle version 12.2.

Fixed issues

Version 3.4.0 of Splunk DB Connect fixes the following issues:

Date resolved Issue number Description
2020-08-07 DBX-5029 data of Decimal(15,2) output to Mysql, data 2 decimal was modified as (.00), it brings up the data inconsistent issues
2020-07-22 DBX-5078 DBXQuery hangs when running 'Execute SQL' Preview
2020-07-08 DBX-5087 DBX output failing periodically when result set is greater than 100
2020-06-24 DBX-5099 Error handling a request: java.lang.NullPointerException: null
2020-06-17 DBX-4933 dbxlookup runs out of memory
2020-05-29 DBX-5030 Customer encountered the error "stderr: UnicodeDecodeError: 'utf8'" on DBX version 3.3.0, but not on DBX version 3.1.4 when doing "| dbxquery"
2020-05-06 DBX-4988 Warnings of python.version on post Splunk 8

Known issues

Version 3.4.0 of Splunk DB Connect contains the following known issues. If no issues appear below, no issues have yet been reported:

Date filed Issue number Description
2020-10-26 DBX-5237 dbxquery_bridge.py causing CLOSE_WAIT issues
2020-10-22 DBX-5233 `dbxquery` command in 3.4.0 stuck when running against Japanese column
2020-09-17 DBX-5188 DB Connect does not handle usernames with email addresses: users cannot remove DB Connect connection - receives error: "Splunkd error: HTTP 404 -- User does not exist"

Under the /opt/splunk/etc/apps/splunk_app_db_connect/metadata/local.meta file, the user was listed as you see below.

[db_connections/test_connection] access = read : [ admin, db_connect_admin, db_connect_user ], write : [ admin, db_connect_admin ] export = none owner = example%email.com version = modtime = 1599848885.288809000

Customer changed the user to be "admin", restarted splunk and were able to delete the connection.

Similar to: https://community.splunk.com/t5/All-Apps-and-Add-ons/After-upgrade-Splunk-DB-connect-2-3-1-gt-3-1-1-we-can-t-delete/td-p/374500

2020-06-22 DBX-5096 After upgrade DBconnect 3.3+ dbxquery breaks with error "Error in 'dbxquery' command: External search command exited unexpectedly with non-zero error code 1"

DBconnect 3.3+ modifies the parameters for the dbxquery command.

If you had a local override from a DBX version older than 3.3, this will contain configuration and arguments for the old version of the command.

Solution is to remove/review the whole [dbxquery] stanza from commands.conf in $SPLUNK_HOME/etc/apps/splunk_app_db_connect/local

Last modified on 09 November, 2020

This documentation applies to the following versions of Splunk® DB Connect: 3.4.0

Was this documentation topic helpful?

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters