All Apps and Add-ons

Splunk DB Connect: Why am I getting "The value is not set for the parameter number 1" when updating the SQL query in the Edit Input panel?

pkeller
Contributor

As I go through the manual process of trying to migrate queries from dbConnect v1.x to dbConnect 3.1.3, I'm having issues with the Edit Input panel.

I follow the steps.

  1. Choose a valid connection - check
  2. Browse structure and type SQL .... - check
  3. Pick a rising column and set the checkpoint value - check
  4. Update SQL to accept the checkpoint value and make sure it works.

This is where I run into a problem.The second I start typing "WHERE TIME_STAMP > ? .... The Rising Column dropdown completely empties out and the query returns:

com.microsoft.sqlserver.jdbc.SQLServerException: The value is not set for the parameter number 1. ( No results found )

This makes me unable to save the query and actually set a Rising Column and a Checkpoint Value

If I execute the same query using EVENT_TIME, things work ... but, both EVENT_TIME and TIME_STAMP are 'bigint' objects, and they both show up in the batch query results, so the question would be, why is TIME_STAMP an invalid field to use as a rising column in dbConnect 3 but works perfectly in dbConnect 1?

The target database is MS SQL Server

0 Karma

vishaltaneja070
Motivator

You can use it but it is not recommended to have date time column as rising column.

And also, one you put where TIME_STAMP > 1, then you will be able to see the rising column list again.

0 Karma
Get Updates on the Splunk Community!

Observe and Secure All Apps with Splunk

  Join Us for Our Next Tech Talk: Observe and Secure All Apps with SplunkAs organizations continue to innovate ...

Splunk Decoded: Business Transactions vs Business IQ

It’s the morning of Black Friday, and your e-commerce site is handling 10x normal traffic. Orders are flowing, ...

Fastest way to demo Observability

I’ve been having a lot of fun learning about Kubernetes and Observability. I set myself an interesting ...