# Tracking\_column not found in dataset
**URL:** https://discuss.elastic.co/t/tracking-column-not-found-in-dataset/99044
**Category:** Logstash
**Created:** [August 31, 2017, 7:59pm UTC](https://discuss.elastic.co/t/tracking-column-not-found-in-dataset/99044 "2017-08-31T19:59:33Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@aliyesami](https://discuss.elastic.co/u/aliyesami)
#### Post date: [August 31, 2017, 7:59pm UTC](https://discuss.elastic.co/t/tracking-column-not-found-in-dataset/99044/1 "2017-08-31T19:59:33Z")
what does this error means? my lostash load is continuing but keep getting this intermittent messages .
I checked the tracking column "TXN\_PROCESS\_DATE" for nulls but it doesn't have any null values and its of date type.
> [2017-08-31T15:50:00,046][INFO][logstash.inputs.jdbc] (0.009000s) SELECT TXN\_ID,TXN\_PROCESS\_DATE,TRANSP\_ID,TRANSP\_CLASS,EXT\_PLAZA\_ID,EXT\_LANE\_ID,EXT\_LANE\_TYPE\_CODE,EXT\_DATE\_TIME,TRANSP\_CUR\_BAL,AVC\_CLASS,TOLL\_AMT\_CHARGED,TOLL\_AMT\_COLLECTED,TOLL\_AMT\_FULL,CREDIT\_LIST\_UPDATE\_FLAG,TRANS\_SOURCE,REVCLASS\_REV\_CLASS\_CODE,PAYMENT\_METHOD\_CODE,ENT\_PLAZA\_ID,ENT\_DATE\_TIME,ENT\_LANE\_ID,ENT\_LANE\_TYPE\_CODE,AGENCY\_REJECT\_CODE,MSG\_ID,TRANSP\_INTERNAL\_NUM,UFM\_PAYMENT\_CODE,VEH\_LIC\_NUM,STATE\_ID\_CODE,ORIG\_TXN\_ID from TAB1 WHERE TXN\_PROCESS\_DATE \>TIMESTAMP '2017-08-20 08:29:00.000000 +00:00'
> [2017-08-31T15:50:00,047][WARN][logstash.inputs.jdbc] tracking\_column not found in dataset. {:tracking\_column=\>"TXN\_PROCESS\_DATE"}
---
### Author:  [@guyboertje](https://discuss.elastic.co/u/guyboertje)
#### Post date: [September 4, 2017, 3:21pm UTC](https://discuss.elastic.co/t/tracking-column-not-found-in-dataset/99044/2 "2017-09-04T15:21:14Z")
To be honest, I don't know.
I have checked the code and modified some tests to see if I can simulate it.
Some common issues:
- Query is not sorted ascending on the `tracking_column` value.
- The column name is changed to lowercase by the SQL library we use but the UPPERCASE column name is used in the tracking column setting.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 2, 2017, 3:21pm UTC](https://discuss.elastic.co/t/tracking-column-not-found-in-dataset/99044/3 "2017-10-02T15:21:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
---
### Author:  [@PhaedrusTheGreek](https://discuss.elastic.co/u/PhaedrusTheGreek)
#### Post date: [November 9, 2017, 4:26pm UTC](https://discuss.elastic.co/t/tracking-column-not-found-in-dataset/99044/4 "2017-11-09T16:26:51Z")
Also make sure you select the tracking column in the SQL statement. For example, if you do not have select \*, then if you have:
```auto
tracking_column => "TXN_PROCESS_DATE"
```
Make sure you also do
```auto
select TXN_PROCESS_DATE, OTHER_COLUMN, ETC from ...
```