# Issue with monitoring Oracle Databases with Logstash

**URL:** <https://discuss.elastic.co/t/issue-with-monitoring-oracle-databases-with-logstash/49368>\
**Category:** Logstash\
**Created:** [May 6, 2016, 3:21am UTC](https://discuss.elastic.co/t/issue-with-monitoring-oracle-databases-with-logstash/49368 "2016-05-06T03:21:07Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![r4z0rw1r3666](https://avatars.discourse-cdn.com/v4/letter/r/e79b87/32.png) [@r4z0rw1r3666](https://discuss.elastic.co/u/r4z0rw1r3666)\
**Post date:** [May 6, 2016, 3:21am UTC](https://discuss.elastic.co/t/issue-with-monitoring-oracle-databases-with-logstash/49368/1 "2016-05-06T03:21:07Z")

</div>

Hello,

I'm having some issues with Logstash and monitoring a single Oracle database. Logstash takes 30 seconds to  
"warm up" before generating data, for a further 45 seconds before promptly imploding. Error that I've captured is:

Attempted to send a bulk request to Elasticsearch configured at '["[http://localhost:9200/](http://localhost:9200/)"]', but an error occurred and it failed! Are you sure you can reach elasticsearch from this machine using the configuration provided? {:error\_message=\>"Cannot serialize instance of: Sequel::SQL::Blob",

I'm wondering if there are any logstash guru's who can shine some light on this particular issue?

Cheers.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 6, 2016, 3:26am UTC](https://discuss.elastic.co/t/issue-with-monitoring-oracle-databases-with-logstash/49368/2 "2016-05-06T03:26:36Z")

</div>

Can you paste your entire config? What version are you on? What OS?

---

<div class="post-metadata">

**Author:** ![r4z0rw1r3666](https://avatars.discourse-cdn.com/v4/letter/r/e79b87/32.png) [@r4z0rw1r3666](https://discuss.elastic.co/u/r4z0rw1r3666)\
**Post date:** [May 6, 2016, 3:43am UTC](https://discuss.elastic.co/t/issue-with-monitoring-oracle-databases-with-logstash/49368/3 "2016-05-06T03:43:30Z")

</div>

Hello,

Thanks so much for your assistance on this.

Configuration is as follows:

Host OS - OEL 6.7  
JDK - 8 update 92  
Logstash Version - 2.3.2

Logstash Config:  
input {  
jdbc {  
jdbc\_validate\_connection =\> true  
jdbc\_connection\_string =\> "_"  
jdbc\_user =\> "_"  
jdbc\_password =\> "_"  
jdbc\_driver\_library =\> "/opt/ojdbc6.jar"  
jdbc\_driver\_class =\> "Java::oracle.jdbc.driver.OracleDriver"  
statement =\> "SELECT \* FROM V$ACTIVE\_SESSION\_HISTORY WHERE SAMPLE\_TIME \> :sql\_last\_value"  
last\_run\_metadata\_path =\> "/tmp/logstash-oradb.lastrun"  
record\_last\_run =\> true  
schedule =\> "_/6 \* \* \* \*"  
}  
}  
filter {  
# Set the timestamp to that of the ASH sample, not current time.  
mutate { convert =\> ["sample\_time" , "string"]}  
date { match =\> ["sample\_time", "ISO8601"]}  
}  
output {  
stdout { codec =\> rubydebug }  
elasticsearch {  
index =\> "oracle-"  
hosts =\> "localhost"}  
}

Let me know if you need anything further.

---

<div class="post-metadata">

**Author:** ![r4z0rw1r3666](https://avatars.discourse-cdn.com/v4/letter/r/e79b87/32.png) [@r4z0rw1r3666](https://discuss.elastic.co/u/r4z0rw1r3666)\
**Post date:** [May 16, 2016, 1:36am UTC](https://discuss.elastic.co/t/issue-with-monitoring-oracle-databases-with-logstash/49368/4 "2016-05-16T01:36:02Z")

</div>

Just bumping this post to the top, in the hope that a logstash expert can shine some more light on this particular issue.

---

<div class="post-metadata">

**Author:** ![negash](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/negash/32/9838_2.png) [@negash](https://discuss.elastic.co/u/negash)\
**Post date:** [May 19, 2016, 8:38pm UTC](https://discuss.elastic.co/t/issue-with-monitoring-oracle-databases-with-logstash/49368/5 "2016-05-19T20:38:57Z")

</div>

check the incoming data is possible there is a "break" line , I had a binary (20) in a single column . I just decided to check out the insert in other tables and everything worked

---

<div class="post-metadata">

**Author:** ![bizkit](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bizkit/32/11012_2.png) [@bizkit](https://discuss.elastic.co/u/bizkit)\
**Post date:** [July 21, 2016, 5:10pm UTC](https://discuss.elastic.co/t/issue-with-monitoring-oracle-databases-with-logstash/49368/6 "2016-07-21T17:10:49Z")

</div>

Is there any update on this? My org has ran into the same error on 2.3 but do not run into this error or 2.0.

Just seeing if you were able to fix this. We only noticed the issue when connecting to Oracle DB.

Thanks.

---

<div class="post-metadata">

**Author:** ![r4z0rw1r3666](https://avatars.discourse-cdn.com/v4/letter/r/e79b87/32.png) [@r4z0rw1r3666](https://discuss.elastic.co/u/r4z0rw1r3666)\
**Post date:** [July 24, 2016, 11:09pm UTC](https://discuss.elastic.co/t/issue-with-monitoring-oracle-databases-with-logstash/49368/7 "2016-07-24T23:09:11Z")

</div>

Not from my point of view. I've alpha 4 seems to last longer, but still implodes.

I believe there are 2 issues. Firstly, it's to do with my proof of concept architecture I had. Haven't had the time to revisit my updated architecture, with 1 logstash instance as a message forwarder into kafka into a second logstash instance (worker) in elastic. Hope to revisit this in the coming week or two.

Secondly, it's the sheer volume in question, which gives my first issue slightly more credit. I've been thinking about what table, with limited diagnostic information I could use then scale up from there.

Does that make sense? Or have you built it out are still having this issue?

---

<div class="post-metadata">

**Author:** ![lyxhaven](https://avatars.discourse-cdn.com/v4/letter/l/b9bd4f/32.png) [@lyxhaven](https://discuss.elastic.co/u/lyxhaven)\
**Post date:** [October 11, 2016, 4:44pm UTC](https://discuss.elastic.co/t/issue-with-monitoring-oracle-databases-with-logstash/49368/8 "2016-10-11T16:44:21Z")

</div>

I am having the same issue. Perhaps that's because some of my db columns contain JSON objects.

Is there a solution for this ?

---

<div class="post-metadata">

**Author:** ![NSK](https://avatars.discourse-cdn.com/v4/letter/n/a4c791/32.png) [@NSK](https://discuss.elastic.co/u/NSK)\
**Post date:** [October 21, 2016, 10:31pm UTC](https://discuss.elastic.co/t/issue-with-monitoring-oracle-databases-with-logstash/49368/9 "2016-10-21T22:31:07Z")

</div>

Facing the same issue in logstash 2.4.0

LogStash::Json::GeneratorError: Cannot serialize instance of: Sequel::SQL::Blob  
jruby\_dump at /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/json.rb:53  
to\_json at /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-event-2.4.0-java/lib/logstash/event.rb:145  
encode at /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-codec-json\_lines-2.1.3/lib/logstash/codecs/json\_lines.rb:48  
receive at /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-stdout-2.0.6/lib/logstash/outputs/stdout.rb:55  
multi\_receive at /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/outputs/base.rb:109  
each at org/jruby/RubyArray.java:1613  
multi\_receive at /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/outputs/base.rb:109  
worker\_multi\_receive at /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/output\_delegator.rb:130  
multi\_receive at /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/output\_delegator.rb:114  
output\_batch at /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/pipeline.rb:301  
each at org/jruby/RubyHash.java:1342  
output\_batch at /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/pipeline.rb:301  
worker\_loop at /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/pipeline.rb:232  
start\_workers at /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.4.0-java/lib/logstash/pipeline.rb:201

Any assistance would be greatly appreciated

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 4:33am UTC](https://discuss.elastic.co/t/issue-with-monitoring-oracle-databases-with-logstash/49368/10 "2017-07-06T04:33:14Z")

</div>


