# JDBC input Value tracking, "Can't dup Fixnum" **URL:** \ **Category:** Logstash\ **Created:** [September 30, 2018, 11:00am UTC](https://discuss.elastic.co/t/jdbc-input-value-tracking-cant-dup-fixnum/150473 "2018-09-30T11:00:23Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![muyuqj](https://avatars.discourse-cdn.com/v4/letter/m/85e7bf/32.png) [@muyuqj](https://discuss.elastic.co/u/muyuqj)\ **Post date:** [September 30, 2018, 11:00am UTC](https://discuss.elastic.co/t/jdbc-input-value-tracking-cant-dup-fixnum/150473/1 "2018-09-30T11:00:23Z")
rufus-scheduler intercepted an error: 2030 job: 2030 Rufus::Scheduler::CronJob "\*/1 \* \* \* \*" {} 2030 error: 2030 2030 2030 TypeError 2030 can't dup Fixnum 2030 org/jruby/RubyKernel.java:1882:in `dup' 2030 uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/date/format.rb:838:in`\_parse' 2030 uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/date.rb:1830:in `parse' 2030 /home/es/logstash-6.4.1/vendor/bundle/jruby/2.3.0/gems/logstash-input-jdbc-4.3.13/lib/logstash/plugin_mixins/jdbc/value_tracking.rb:87:in`set\_value' 2030 /home/es/logstash-6.4.1/vendor/bundle/jruby/2.3.0/gems/logstash-input-jdbc-4.3.13/lib/logstash/plugin\_mixins/jdbc/jdbc.rb:237:in `execute_statement' 2030 /home/es/logstash-6.4.1/vendor/bundle/jruby/2.3.0/gems/logstash-input-jdbc-4.3.13/lib/logstash/inputs/jdbc.rb:277:in`execute\_query' 2030 /home/es/logstash-6.4.1/vendor/bundle/jruby/2.3.0/gems/logstash-input-jdbc-4.3.13/lib/logstash/inputs/jdbc.rb:258:in `block in run' 2030 /home/es/logstash-6.4.1/vendor/bundle/jruby/2.3.0/gems/rufus-scheduler-3.0.9/lib/rufus/scheduler/jobs.rb:234:in`do\_call' 2030 /home/es/logstash-6.4.1/vendor/bundle/jruby/2.3.0/gems/rufus-scheduler-3.0.9/lib/rufus/scheduler/jobs.rb:258:in `do_trigger' 2030 /home/es/logstash-6.4.1/vendor/bundle/jruby/2.3.0/gems/rufus-scheduler-3.0.9/lib/rufus/scheduler/jobs.rb:300:in`block in start\_work\_thread' 2030 /home/es/logstash-6.4.1/vendor/bundle/jruby/2.3.0/gems/rufus-scheduler-3.0.9/lib/rufus/scheduler/jobs.rb:299:in `block in start_work_thread' 2030 org/jruby/RubyKernel.java:1292:in`loop' 2030 /home/es/logstash-6.4.1/vendor/bundle/jruby/2.3.0/gems/rufus-scheduler-3.0.9/lib/rufus/scheduler/jobs.rb:289:in `block in start\_work\_thread' 2030 tz: 2030 ENV['TZ']: 2030 Time.now: 2018-09-30 03:52:00 -0700 2030 scheduler: 2030 object\_id: 2008 2030 opts: 2030 {:max\_work\_threads=\>1} 2030 frequency: 0.3 2030 scheduler\_lock: #Rufus::Scheduler::NullLock:0x12fe432a 2030 trigger\_lock: #Rufus::Scheduler::NullLock:0x67666c6b 2030 uptime: 623.324875 (10m23s324) 2030 down?: false 2030 threads: 2 2030 thread: #Thread:0x3a2a6394 2030 thread\_key: rufus\_scheduler\_2008 2030 work\_threads: 1 2030 active: 1 2030 vacant: 0 2030 max\_work\_threads: 1 2030 mutexes: {} 2030 jobs: 1 2030 at\_jobs: 0 2030 in\_jobs: 0 2030 every\_jobs: 0 2030 interval\_jobs: 0 2030 cron\_jobs: 1 2030 running\_jobs: 1 2030 work\_queue: 0 what is matter about this problem ? ---
**Author:** ![guyboertje](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guyboertje/32/31592_2.png) [@guyboertje](https://discuss.elastic.co/u/guyboertje)\ **Post date:** [October 2, 2018, 10:00am UTC](https://discuss.elastic.co/t/jdbc-input-value-tracking-cant-dup-fixnum/150473/2 "2018-10-02T10:00:26Z")
The error is in `/plugin_mixins/jdbc/value_tracking.rb:87:in 'set_value'` where the tracking column datatype is `Date` but it is getting a number not a date. Have you recently changed the jdbc\_input's tracking column settings? If so then you need to set `clean_run => true` once to clear out the old tracking value. ---
**Author:** ![muyuqj](https://avatars.discourse-cdn.com/v4/letter/m/85e7bf/32.png) [@muyuqj](https://discuss.elastic.co/u/muyuqj)\ **Post date:** [October 17, 2018, 11:42am UTC](https://discuss.elastic.co/t/jdbc-input-value-tracking-cant-dup-fixnum/150473/3 "2018-10-17T11:42:53Z")
thanks for your answers,I have solved this problem by configure tracking\_column\_type as numeric type. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 14, 2018, 11:42am UTC](https://discuss.elastic.co/t/jdbc-input-value-tracking-cant-dup-fixnum/150473/4 "2018-11-14T11:42:55Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.