Getting Data In

Db connect HTTP 400 Error

Nawab
Communicator

I am getting below error on my dbconnect, every thing was working fine

HTTP Error 400, HEC response body: {"text":"Invalid data format","code":6,"invalid-event-number":15}, trace: HttpResponseProxy{HTTP/1.1 400 Bad Request [Date: Mon, 29 Sep 2025 10:35:01 GMT, Content-Type: application/json; charset=UTF-8, X-Content-Type-Options: nosniff, Content-Length: 65, Vary: Authorization, Connection: Keep-Alive, X-Frame-Options: SAMEORIGIN, Server: Splunkd] ResponseEntityProxy{[Content-Type: application/json; charset=UTF-8,Content-Length: 65,Chunked: false]}}

Labels (1)
0 Karma

isoutamo
SplunkTrust
SplunkTrust

Can you tell more about this?

  • Where you are getting this?
  • What you have actually try/done?
  • What is your environment?
  • What DB you have?
  • What are your versions (splunk, dbx, jdbc drivers/packages, OS, target db etc.)
  • Is this db_input or something else?
  • Or are you initially configure your DB Connection to source DB?
0 Karma

Nawab
Communicator

no we haven't changed anything on our query

0 Karma

PrewinThomas
Motivator

@Nawab 

Have you modified any of your query? Can you specify more details.

The error highlights here can be of multiple reasons 

{"text":"Invalid data format","code":6,"invalid-event-number":15}


Regards,
Prewin
If this answer helped you, please consider marking it as the solution or giving a Karma. Thanks!

0 Karma
Get Updates on the Splunk Community!

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...