This documentation does not apply to the most recent version of Splunk® DB Connect.
For documentation on the most recent version, go to the latest release.
Download topic as PDF
Release notes
Fixed issues
Fixed date | Defect number | Description |
---|---|---|
2017-02-15 | DBX-3644 | Complex dbxlookup SQL statements are cut short, producing syntax errors |
2017-02-15 | DBX-3541 | Summary index populating search runs over all time |
2017-02-15 | DBX-3483 | On Windows, log file rotation will cause splunkd.log errors. |
2017-02-15 | DBX-3358 | advanced mode inputs in non-dbx app context cause 404 errors. |
2017-02-15 | DBX-3349 | dbx_health sourcetype definition doesn't collect query logs. |
2017-02-15 | DBX-3265 | Generating command duplicates records through dbxoutput. |
2017-02-15 | DBX-3264 | mvappend query has Unicode formatting appended to string in DB2 Output, causing additional unwanted characters. |
2017-02-15 | DBX-3240 | Under high load, DBconnect 2 inputs.conf can cause "local.meta outstanding write." error in splunkd.log. |
2017-02-15 | DBX-3206 | Unclear error log messages when dbxoutput attempts to use a private saved search. |
2017-02-15 | DBX-3178 | Cannot establish connection with Oracle SSL on the first try. |
2017-02-15 | DBX-3177 | Unclear error message when user is not allowed to edit SSL related options due to capabilities restriction. |
2017-02-15 | DBX-3149 | SQL editor "execute" button is blocked by UI errors. |
2017-02-15 | DBX-3067 | Input with an empty sourcetype can be saved. |
2017-02-15 | DBX-3056 | Invalid parameter value in a query does not return an error. |
2017-02-15 | DBX-3051 | dbxoutput memory usage is high. |
2017-02-15 | DBX-3050 | No refresh button on lookup preview result. |
2017-02-15 | DBX-2980 | Selecting an item in Operation page will trigger a dbxquery execution that may cause a performance issue. |
2017-02-15 | DBX-2877 | Errors of identity or connection delay the page display. |
2017-02-15 | DBX-2833 | Error message appears when creating an identity in Splunk 6.3 on Windows. |
Known issues
Publication date | Defect number | Description |
---|---|---|
2017-02-24 | DBX-3871 | In Linux operating system, the input cannot work properly after migration from DB Connect 2 if its name contains upper class character. Workaround: Rename the checkpoint name in |
2017-02-14 | DBX-3841 | DB Connect 3.0.0 does not support a new installation of Splunk Add-on for MySQL or Splunk Add-on for Nagios Core. Additionally, the template files included in Splunk Add-on for McAfee, Splunk Add-on for Oracle Database, and Splunk Add-on for Microsoft SQL will not work if copied into DB Connect 3. |
2017-02-09 | DBX-3831 | Task server could not start on Windows when splunk service is logged on with a domain user |
2017-02-08 | DBX-3823 | When upgrading from version 2.4 to 3.0 on Ubuntu, the RPC task server is not reliably killed and may prevent starting the new server. |
2017-02-09 | DBX-3829 | Connection used by scheduled jobs will not be refreshed when identity was updated. |
2017-01-26 | DBX-3809 | A disabled output definition can still be used in an alert action. |
2017-01-21 | DBX-3783 | If an input has just been deleted, a new input with the same name cannot be created. |
2017-01-20 | DBX-3781 | Once a column has been chosen as input timestamp, current index time option cannot be chosen. |
2017-01-20 | DBX-3779 | [MySQL] The connection fails when the hostname field contains a space character. |
2017-01-20 | DBX-3778 | app.conf and dbx_settings.conf are not replicated in search head cluster environments |
2017-01-19 | DBX-3746 | customized JAVA_HOME setting is ignored by dbxoutput when launched from modular alert. |
2017-01-13 | DBX-3720 | Informix and DB2 drivers conflict. |
2017-01-09 | DBX-3706 | Creating an input with an already-used name does not cause a warning message. |
2016-12-16 | DBX-3616 | Output is not supported when using Cisco CIS JDBC driver. |
2016-12-15 | DBX-3613 | Could not load tables with no category/schema from CIS. |
2016-12-15 | DBX-3610 | "TIMESTAMP WITH TIME ZONE" and "TIMESTAMP WITH LOCAL TIME ZONE" can not be used in rising column input. |
2016-12-06 | DBX-3570 | Reload API will reload both output and input tasks. |
2016-11-01 | DBX-3371 | Incorrect output result preview for multiple values |
2016-10-11 | DBX-3256 | Failure to enable client certification because a key or certificate is missing in local/certs does not produce an error message. |
2016-04-21 | DBX-2820 | RPC server failure provides incomplete information in the error log. |
2016-02-12 | DBX-2623 | v1 to v2 migration scripts fail on special characters. |
Last modified on 28 February, 2017
NEXT Credits |
This documentation applies to the following versions of Splunk® DB Connect: 3.0.0
Feedback submitted, thanks!