All Apps and Add-ons

DBConnect parameter 1 error with rising input

nick405060
Motivator

3.1.3, gives me a java.sql.SQLException: Invalid parameter index 1. error, or a Parameter #1 has not been set error. Any clues? I'm literally just trying to do the most basic rising input possible for a SELECT * query and I had the same issue with another database last week, which all of a sudden started working.

0 Karma
1 Solution

nick405060
Motivator

The app interface claims to populate the SQL query template for you on the right-hand side, but it does so incorrectly: it only populates half of it. It populates the rising column in the query template but not the table name. Select the table, select batch type rising, select the rising column, copy and paste the SQL template into the SQL section but modify the table name.

It sounds like a silly problem that you should have caught, but it's not. The app claims to populate the SQL query template for you, but it only populates part of it. Ridiculously unexpected. For anyone having this problem, this is a Splunk QA team problem not a user problem.

View solution in original post

nick405060
Motivator

The app interface claims to populate the SQL query template for you on the right-hand side, but it does so incorrectly: it only populates half of it. It populates the rising column in the query template but not the table name. Select the table, select batch type rising, select the rising column, copy and paste the SQL template into the SQL section but modify the table name.

It sounds like a silly problem that you should have caught, but it's not. The app claims to populate the SQL query template for you, but it only populates part of it. Ridiculously unexpected. For anyone having this problem, this is a Splunk QA team problem not a user problem.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...