Splunk Enterprise

why the DB Connect input fetch the same data twice in a single run?

akarivaratharaj
Communicator

I have an input created in DB Connect app to few the necessary rows from a DB2 table. The job is scheduled to run on daily basis and to fetch only the previous day's data.

I have left the "Max rows to retrieve" and "Fetch size" to default settings. Whenever my job runs, by default it is logging the same records twice. I am not sure what is causing this issue.

I have attached screenshot of the entries belong to a primary key field where two events are indexed for each record.

Could anyone help me in troubleshooting the issue?

Labels (1)
Tags (1)
0 Karma

akarivaratharaj
Communicator

Could anyone please help me to troubleshoot this issue? I need this to be fixed as soon as possible.

0 Karma

isoutamo
SplunkTrust
SplunkTrust

Hi

How you have defined that input on your HF (DB Connect) node? Are you sure that those events are really twice here instead of you have e.g. set both INDEX EXTRACTIONS on HF side and KV_MODE=JSON on SH side?

r. Ismo

0 Karma

akarivaratharaj
Communicator

I have created my input in DB Connect app directly from the UI of Splunk Enterprise. As I don't have permission for operations related task, I am unable to check that.

I have observed that my another input also index the data events twice. Not sure if these duplication issue is because of the fetch size which we give it in the input schedule (By the way I have left them blank to apply with default settings)

0 Karma

akarivaratharaj
Communicator

Can I get any other suggestion on trouble shooting this issue?

0 Karma
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!

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...

Design, Compete, Win: Submit Your Best Splunk Dashboards for a .conf26 Pass

Hello Splunkers,  We’re excited to kick off a Splunk Dashboard contest! We know that dashboards are a primary ...

May 2026 Splunk Expert Sessions: Security & Observability

Level Up Your Operations: May 2026 Splunk Expert Sessions Whether you are refining your security posture or ...