All Apps and Add-ons

Splunk DB Connect 3: Error message -- Splunk DB Connect is not using the "Checkpoint Value" information for the request

BrunoMonti
Engager

I made a query to use in the dbconnect 3 as a Rising Input Type. But, every time the job runs i got the same information. The "Checkpoint Value" has stopped and the dbconnect are not using the "Checkpoint Value" information to do the new request. So, Looking into the logs I found the error:

2017-10-19 17:40:00.311 -0200 [QuartzScheduler_Worker-6] INFO c.s.d.s.dbinput.task.DbInputCheckpointRepository - action=save_checkpoint_success checkpoint=Checkpoint{value='2017-08-17 16:02:32.234', appVersion='3.1.1', columnType=93, timestamp='2017-10-19T17:40:00.310-02:00'}
2017-10-19 17:40:00.350 -0200 [QuartzScheduler_Worker-6] WARN c.s.d.s.task.listeners.RecordReaderMetricsListener - action=record_reading_exception {}
java.lang.NullPointerException: null
at com.splunk.dbx.server.dbinput.recordreader.iterator.EventPayloadRecordIterator.next(EventPayloadRecordIterator.java:82)
at com.splunk.dbx.server.dbinput.recordreader.iterator.EventPayloadRecordIterator.next(EventPayloadRecordIterator.java:27)
at com.splunk.dbx.server.dbinput.recordreader.DbInputRecordReader.readRecord(DbInputRecordReader.java:125)
at org.easybatch.core.job.BatchJob.readRecord(BatchJob.java:163)
at org.easybatch.core.job.BatchJob.readAndProcessBatch(BatchJob.java:145)
at org.easybatch.core.job.BatchJob.call(BatchJob.java:78)
at org.easybatch.extensions.quartz.Job.execute(Job.java:59)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)
2017-10-19 17:40:00.350 -0200 [QuartzScheduler_Worker-6] ERROR org.easybatch.core.job.BatchJob - Unable to read next record
java.lang.NullPointerException: null
at com.splunk.dbx.server.dbinput.recordreader.iterator.EventPayloadRecordIterator.next(EventPayloadRecordIterator.java:82)
at com.splunk.dbx.server.dbinput.recordreader.iterator.EventPayloadRecordIterator.next(EventPayloadRecordIterator.java:27)
at com.splunk.dbx.server.dbinput.recordreader.DbInputRecordReader.readRecord(DbInputRecordReader.java:125)
at org.easybatch.core.job.BatchJob.readRecord(BatchJob.java:163)
at org.easybatch.core.job.BatchJob.readAndProcessBatch(BatchJob.java:145)
at org.easybatch.core.job.BatchJob.call(BatchJob.java:78)
at org.easybatch.extensions.quartz.Job.execute(Job.java:59)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)
2017-10-19 17:40:00.350 -0200 [QuartzScheduler_Worker-6] INFO org.easybatch.core.job.BatchJob - Job 'CS' finished with status: FAILED

How can I proceed to fix this error?

0 Karma
1 Solution

BrunoMonti
Engager

Doing the Health check everything looks fine:

JVM installation - DB Connect - This health check item was successful. Everything is good here.
Java Server configuration - DB Connect - This health check item was successful. Everything is good here.
JDBC driver installation - DB Connect - This health check item was successful. Everything is good here.
Data Lab configuration - DB Connect - This health check item was successful. Everything is good here.
Kerberos environment configuration - DB Connect - This health check item was successful. Everything is good here.
DB Connect connections configuration DB Connect - This health check item was successful. Everything is good here.
DB Connect file permission - DB Connect - This health check item was successful. Everything is good here.

I fix this problem modifying the Query converting the ? field to timestamp format:

WHERE CM.MODIFY_DATE > TO_TIMESTAMP(?,'YYYY-MM-DD HH24:MI:SS.FF') ORDER BY CM.MODIFY_DATE ASC

View solution in original post

0 Karma

BrunoMonti
Engager

Doing the Health check everything looks fine:

JVM installation - DB Connect - This health check item was successful. Everything is good here.
Java Server configuration - DB Connect - This health check item was successful. Everything is good here.
JDBC driver installation - DB Connect - This health check item was successful. Everything is good here.
Data Lab configuration - DB Connect - This health check item was successful. Everything is good here.
Kerberos environment configuration - DB Connect - This health check item was successful. Everything is good here.
DB Connect connections configuration DB Connect - This health check item was successful. Everything is good here.
DB Connect file permission - DB Connect - This health check item was successful. Everything is good here.

I fix this problem modifying the Query converting the ? field to timestamp format:

WHERE CM.MODIFY_DATE > TO_TIMESTAMP(?,'YYYY-MM-DD HH24:MI:SS.FF') ORDER BY CM.MODIFY_DATE ASC

0 Karma

jcoates
Communicator

the last checkpoint it saved was

 value='2017-08-17 16:02:32.234', appVersion='3.1.1', columnType=93, timestamp='2017-10-19T17:40:00.310-02:00'

but now it can't read the checkpoint.

I'd run the health checks: http://docs.splunk.com/Documentation/DBX/3.1.1/DeployDBX/CheckInstallationHealth

and then look at the checkpoint file: http://docs.splunk.com/Documentation/DBX/3.1.1/DeployDBX/Createandmanagedatabaseinputs#Choose_input_...

0 Karma
Get Updates on the Splunk Community!

Welcome to the Splunk Community!

(view in My Videos) We're so glad you're here! The Splunk Community is place to connect, learn, give back, and ...

Tech Talk | Elevating Digital Service Excellence: The Synergy of Splunk RUM & APM

Elevating Digital Service Excellence: The Synergy of Real User Monitoring and Application Performance ...

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...