Error reading date '1800-01-01'

arjun_004 · Post by **arjun_004** » Wed May 16, 2007 1:51 am

Hi,
We are facing problems reading date fields with value '1800-01-01'. The database is Teradata and the stage being used is Enterprise stage. It has no issues for all dates starting with century 1900 onwards. Is there a way to ensure the Enterprise stage can read such fields?
Thanks.

baglasumit21 · Post by **baglasumit21** » Thu May 17, 2007 12:49 am

arjun_004 wrote:Hi,
We are facing problems reading date fields with value '1800-01-01'. The database is Teradata and the stage being used is Enterprise stage. It has no issues for all dates starting with century 1900 onwards. Is there a way to ensure the Enterprise stage can read such fields?
Thanks.

As per my knowledge datastage has dates starting from 1900-01-01. so probably it wont read your date.

JoshGeorge · Post by **JoshGeorge** » Thu May 17, 2007 1:35 am

IsValid("Date",'1800-01-01') is a valid date in datastage. Tho IsValid("Date",'0000-01-01') is not.

ray.wurlod · Post by **ray.wurlod** » Thu May 17, 2007 5:26 pm

All valid dates are valid in DataStage. (baglasumit21's understanding is not correct.)

There is no year 0 - the day before 1 Jan 0001AD was 31 Dec 0001BC.

Check your century rules in the interface with Teradata. The restriction might be being imposed there.

DSXchange

Error reading date '1800-01-01'

Error reading date '1800-01-01'

Re: Error reading date '1800-01-01'