<?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: Splunk DB Connect  Tail Input command not working in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Splunk-DB-Connect-Tail-Input-command-not-working/m-p/81053#M181849</link>
    <description>&lt;P&gt;That's probably correct but after a database restart, it started working. I can't say that I can say what the real solution was though. Which is annoying.&lt;/P&gt;</description>
    <pubDate>Thu, 10 Jan 2013 20:49:41 GMT</pubDate>
    <dc:creator>scc00</dc:creator>
    <dc:date>2013-01-10T20:49:41Z</dc:date>
    <item>
      <title>Splunk DB Connect  Tail Input command not working</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-DB-Connect-Tail-Input-command-not-working/m-p/81049#M181845</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I'm trying to use the Tail command for Splunk DB Connect to pull the newest logs into a Splunk Index. Unfortunately, it is not pulling the data, even when I generate new logs. I have tried the DUMP option which works just fine but duplicates the entire database each dump so I don't want to use it. I have configured the Tail option as noted within the documentation and have used the same configurations as I used with the DUMP option but it still does not work. I am not using any specific SQL query either. What am I doing wrong?&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jan 2013 16:42:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-DB-Connect-Tail-Input-command-not-working/m-p/81049#M181845</guid>
      <dc:creator>scc00</dc:creator>
      <dc:date>2013-01-08T16:42:44Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk DB Connect  Tail Input command not working</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-DB-Connect-Tail-Input-command-not-working/m-p/81050#M181846</link>
      <description>&lt;P&gt;One thing I'm discovering is that the "rising column" and "log date" column names must be specified in ALL CAPS or they won't be recognized. There may be other issues with your particular query as well. I got some insight from checking the $SPLUNK_HOME/var/log/splunk/dbx.log file.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jan 2013 20:41:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-DB-Connect-Tail-Input-command-not-working/m-p/81050#M181846</guid>
      <dc:creator>pmagee</dc:creator>
      <dc:date>2013-01-08T20:41:58Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk DB Connect  Tail Input command not working</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-DB-Connect-Tail-Input-command-not-working/m-p/81051#M181847</link>
      <description>&lt;P&gt;Well I tried the CAPS option with no results. Though I did check the dbx.log file and found two SQL exceptions. I'm checking with my DBAs but I doubt the database is full. Any other thoughts?&lt;/P&gt;

&lt;P&gt;dbx5836:WARN:PooledConnectionFactory - Pooled Connection validation failed: com.splunk.dbx.sql.Database$DatabaseValidationException: Error validating database: java.sql.SQLException: I/O Error: No space left on device&lt;BR /&gt;
dbx5836:ERROR:TailDatabaseMonitor - Error while executing database monitor: java.sql.SQLException: The column "ERR_ADD_DATE" is not present in the result set&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 13:04:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-DB-Connect-Tail-Input-command-not-working/m-p/81051#M181847</guid>
      <dc:creator>scc00</dc:creator>
      <dc:date>2020-09-28T13:04:22Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk DB Connect  Tail Input command not working</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-DB-Connect-Tail-Input-command-not-working/m-p/81052#M181848</link>
      <description>&lt;P&gt;Based on your errors it looks like your connection to the database is failing. I would suspect that there is a space shortage in the database, probably in regards to the audit trail. The audit trail can't expand, so the login fails, which is why the column doesn't show up in the result set.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Jan 2013 14:47:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-DB-Connect-Tail-Input-command-not-working/m-p/81052#M181848</guid>
      <dc:creator>pmagee</dc:creator>
      <dc:date>2013-01-09T14:47:50Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk DB Connect  Tail Input command not working</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-DB-Connect-Tail-Input-command-not-working/m-p/81053#M181849</link>
      <description>&lt;P&gt;That's probably correct but after a database restart, it started working. I can't say that I can say what the real solution was though. Which is annoying.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jan 2013 20:49:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-DB-Connect-Tail-Input-command-not-working/m-p/81053#M181849</guid>
      <dc:creator>scc00</dc:creator>
      <dc:date>2013-01-10T20:49:41Z</dc:date>
    </item>
  </channel>
</rss>

