<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: dbxquery command: external search exited unexpectedly in Security</title>
    <link>https://community.splunk.com/t5/Security/dbxquery-command-external-search-exited-unexpectedly/m-p/755922#M18543</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/314209"&gt;@ankit13&lt;/a&gt;,&lt;BR /&gt;&lt;BR /&gt;The issue may be on your checkpoint value format. Can you, just for an experimentation purpose, pick another field like a numerical one and use it just to see if the search loads?&lt;BR /&gt;If it does, then it is all about playing with the datetime format you are passing as initial checkpoint until you can get a format that is working.&lt;BR /&gt;&lt;BR /&gt;Also, the second screenshot showing I/O Operation on a closed writer exception may be telling you that the connection died before returning the results and that is probably because, again,&amp;nbsp;&lt;SPAN&gt;Checkpoint Value current format may be causing interpretation issues on the JDBC query against your database.&lt;BR /&gt;&lt;BR /&gt;Another option is to run a profiler on the DB side to capture exactly how this request is hitting your DB. That would answer all of those questions.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 26 Nov 2025 19:38:17 GMT</pubDate>
    <dc:creator>victor_menezes</dc:creator>
    <dc:date>2025-11-26T19:38:17Z</dc:date>
    <item>
      <title>dbxquery command: external search exited unexpectedly</title>
      <link>https://community.splunk.com/t5/Security/dbxquery-command-external-search-exited-unexpectedly/m-p/755797#M18542</link>
      <description>&lt;P&gt;I am trying to integrate an Oracle database with Splunk using DB Connect. When I attempt to create an input in Data Lab and set the rising column as timestamp, I receive the following error:&lt;/P&gt;&lt;P&gt;“dbxquery command: External search command exited unexpectedly.”&lt;/P&gt;&lt;P data-unlink="true"&gt;I have already reviewed the related article, but the issue still persists.&amp;nbsp;&lt;A href="https://splunk.my.site.com/customer/s/article/After-upgrading-Splunk-DB-connect-from-3-4-0-to-3-17-1" target="_self"&gt;splunk db connect article&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am using Splunk DB Connect version 3.18.&lt;/P&gt;&lt;P&gt;The SQL query runs successfully and returns data when executed normally; the error occurs only when selecting a rising column.&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-left" image-alt="image.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/40872i783DC7935958896D/image-size/medium?v=v2&amp;amp;px=400" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-left" image-alt="image (1).png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/40873iE78B674FD5B60741/image-size/medium?v=v2&amp;amp;px=400" role="button" title="image (1).png" alt="image (1).png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;I have searched the dbxquery logs in internal logs and&amp;nbsp; its shows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Nov 2025 08:53:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/dbxquery-command-external-search-exited-unexpectedly/m-p/755797#M18542</guid>
      <dc:creator>ankit13</dc:creator>
      <dc:date>2025-11-24T08:53:27Z</dc:date>
    </item>
    <item>
      <title>Re: dbxquery command: external search exited unexpectedly</title>
      <link>https://community.splunk.com/t5/Security/dbxquery-command-external-search-exited-unexpectedly/m-p/755922#M18543</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/314209"&gt;@ankit13&lt;/a&gt;,&lt;BR /&gt;&lt;BR /&gt;The issue may be on your checkpoint value format. Can you, just for an experimentation purpose, pick another field like a numerical one and use it just to see if the search loads?&lt;BR /&gt;If it does, then it is all about playing with the datetime format you are passing as initial checkpoint until you can get a format that is working.&lt;BR /&gt;&lt;BR /&gt;Also, the second screenshot showing I/O Operation on a closed writer exception may be telling you that the connection died before returning the results and that is probably because, again,&amp;nbsp;&lt;SPAN&gt;Checkpoint Value current format may be causing interpretation issues on the JDBC query against your database.&lt;BR /&gt;&lt;BR /&gt;Another option is to run a profiler on the DB side to capture exactly how this request is hitting your DB. That would answer all of those questions.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Nov 2025 19:38:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/dbxquery-command-external-search-exited-unexpectedly/m-p/755922#M18543</guid>
      <dc:creator>victor_menezes</dc:creator>
      <dc:date>2025-11-26T19:38:17Z</dc:date>
    </item>
  </channel>
</rss>

