Data string '01/01/1900' does not match format %yyyy-%mm-%d

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
nani0907
Participant
Posts: 155
Joined: Wed Apr 18, 2007 10:30 am

Post by nani0907 »

you need to bring the date format asyyyy-%mm-%dd' by using to_char option in query. Giva a try
thanks n regards
nani
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

Maybe that is given as default or null value !?
yimwai
Participant
Posts: 46
Joined: Thu Jul 01, 2010 9:34 pm

Post by yimwai »

but why null value or default value can be '01/01/1900'
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

yimwai wrote:but why null value or default value can be '01/01/1900'
That is for you to check.
way246
Participant
Posts: 7
Joined: Wed Sep 01, 2010 9:06 am
Location: Europe

Post by way246 »

yimwai wrote:but why null value or default value can be '01/01/1900'
It is due to insert/update statements run with "" value for datetime field
ramsubbiah
Participant
Posts: 40
Joined: Tue Nov 11, 2008 5:49 am

Post by ramsubbiah »

way246 wrote:
yimwai wrote:but why null value or default value can be '01/01/1900'
It is due to insert/update statements run with "" value for datetime field
the datastage will assign the "1900-01-01" as default(null) value for date field,
Knowledge is Fair,execution is matter!
Post Reply