question Re: Querydatabase processor on teradata db adds millis seconds in logTime when logtime is used for incremental fetch in Archives of Support Questions (Read Only)

Querydatabase processor on teradata db adds millis seconds in logTime when logtime is used for incremental fetch

dhieru — Wed, 15 Nov 2017 01:01:50 GMT

Hi All,

Thanks a lot to this awesome community.

using QueryDatabaseprocessor to fetch data from a teradata db table where logtimestamp is used for incremental fetch. the format for this timestamp is timestamp(0) but it stores the state and add milii seconds for example my timestamp is in the DB

2017-11-11 20:30:32

and when the querydatabase porcessor stores the state, it is

2017-11-11 20:30:32.0

so when next time it queries to get incremental data it gives an error invalid time stamp

any help or suggestion

Re: Querydatabase processor on teradata db adds millis seconds in logTime when logtime is used for incremental fetch

dhieru — Wed, 15 Nov 2017 02:28:57 GMT

@Shu @Bryan Bende

any idea, please help Thanks Dheeru

Re: Querydatabase processor on teradata db adds millis seconds in logTime when logtime is used for incremental fetch

Shu_ashu — Sun, 18 Aug 2019 06:20:07 GMT

@dhieru singh

In Maximum-value columns use cast or some other functions that can change the format of 2017-11-11 20:30:32.0 to 2017-11-11 20:30:32

in this screenshot i did cast on the filed name to date and when i see the view state then the processor having just date as the last value.

State:-

Like this way you need to prepare the max value column that can store as 2017-11-11 20:30:32 not with the milliseconds.

Re: Querydatabase processor on teradata db adds millis seconds in logTime when logtime is used for incremental fetch

dhieru — Wed, 15 Nov 2017 05:48:01 GMT

@Shu this worked Thanks a lot, appreciate it