DB Connect not pulling logs

Available Languages

Updated:September 29, 2026
Document ID:SPLK046236

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Apps Add ons

Description

User installed and configured the DB Connect app, and they are able to see the logs in DB Connect while executing the SQL query, but not indexing.
 


Investigation

Files for the DB Connect app were checked and everything was set properly, however, this error was found in Splunkd:
  
ERROR c.s.d.s.dbinput.recordreader.DbInputRecordReader - Unable to check next row from result
set java.sql.SQLException: ORA-12592: TNS:bad packet

Resolution

Splunk is not able to ingest the files because the database is sending a bad packet.  The user in this case will need to review this code which is not related to Splunk, but for the database itself.

More info about it (ORA-12592) can be found here:
Bad Packet Accompanied by Alert Log Errors ORA-3137

Change the timeout parameter in sqlnet.ora on the database to SQLNET.SEND_TIMEOUT=600 to stop getting the bad packet error in the GUI.
 

Revision History

Revision Publish Date Comments
1.0
29-Sep-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products