Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
YPMAL
Contributor III
Contributor III

date data type conflict

Please see the data, job screen shot and output given in the pictures. And please tell why year is not coming properly. Out coming in the tlogrow.

Labels (2)
3 Replies
Anonymous
Not applicable

Because deafault format for date type is different in oracle.
https://i.stack.imgur.com/b1Qsa.png

You can try using TO_DATE(TO_CHAR(RESOLVE_DATE, 'DD-MON-YYYY'), 'DD-MON-YYYY') in your tOracleInput Query.
YPMAL
Contributor III
Contributor III
Author

While loading the data in db I used Talend job only. With date format "yyyy-MM-dd'T'HH:mm:ss". Used timestamp  Oracle datatype to store that. Why it got stored like that as shown in pic in DB. 

 

Thanks for your suggestion. Will appreciate if you suggest solution that can use in tmap.

Anonymous
Not applicable

While we view a date/timestamp field with sql developer ,it is default formatted and shown to us,no matter which format it got loaded.
You should change the NLS setting in db. Reffer below screenshot.
https://i.stack.imgur.com/b1Qsa.png