Release notes

Version 3.3.0 of Splunk DB Connect was released on March 13, 2020.

New and changed features

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

• Support for JRE 11 and OpenJDK 11.0
• Improved performance when launching DBConnect in dbxquery mode.

Fixed issues

Version 3.3.0 of Splunk DB Connect fixes the following issues:

Date resolved	Issue number	Description
2020-01-17	DBX-3778	The app.conf and dbx_settings.conf are not replicated under cluster environment
2020-01-03	DBX-4436	dbxquery fails with an OutOfMemoryError when returning large data set i.e. GB of data
2019-11-06	DBX-4799	DB Connect 3.1.4 Not working with Solaris Adaptive Server Enterprise/16.0 SP02 PL07
2019-10-08	DBX-4616	Need to add extra backlash (escape) in GUI to be able to get literal backslash in query, but this breaks the query in the configuration file, preventing it from running after saving

Known issues

Version 3.3.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-08-24	DBX-5155	Customer gets 'visualization not found' error when running queries in the SQL editor Workaround: They have been making the visualizations for MLTK local as a temp workaround.
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" Workaround: 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
2020-04-29	DBX-5040	tail_rising_column_init_ckpt_value missing from spec file, creating "Invalid key in stanza" warning on startup of splunk Workaround: add the following line underneath the [<name>] heading in $SPLUNK_HOME/etc/apps/splunk_app_db_connect/README/db_inputs.conf.spec: tail_rising_column_init_ckpt_value = <string>
2020-04-26	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-04-26	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-03-29	DBX-4998	dbxlookup fails after upgrade to 3.3.0
2020-03-24	DBX-4988	Warnings of python.version on post Splunk 8 Workaround: .../etc/apps/splunk_app_db_connect/README/. Neither of these files exist by default. commands.conf.spec [<STANZA_NAME>] python.version = {default|python|python2|python3} Optional setting. Requires 8.0+ For Python scripts only, selects which Python version to use. Set to either "default" or "python" to use the system-wide default Python version. Optional. Default: Not set; uses the system-wide Python version. restmap.conf.spec [script:<uniqueName>] python.version={default|python|python2|python3} Optional setting. Requires 8.0+ For Python scripts only, selects which Python version to use. Set to either "default" or "python" to use the system-wide default Python version. Optional. Default: Not set; uses the system-wide Python version.
2020-02-16	DBX-4933	dbxlookup runs out of memory