why the Baan date with empty value is different after migrating from Baan oracle 7.3.4 to 8.1.7 ?
for example :
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Product
1 select to_char(t$csdt,'YYYY/MM/DD')
2 from baan.ttdsls041660
3* where t$orno = 123456
SQL> /
TO_CHAR(T$
----------
0000/00/00
Oracle7 Server Release 7.3.4.0.1 - Production
SQL> /
TO_CHAR(T$CSDT,'YYYY/MM/DD')
-------------------------------------------------------
9999/01/01

Thanks.

The value hasn't changed. Oracle's 8i format mask for dates do not support date values below the range of 01/01/-4712. The Baan null date value of 01/01/-9999 is still being input by the Baan/Oracle driver which is written in Oracle's OCI (Oracle Call Interface) which does not validate date values entered through it. The value 00/00/0000 just means that the date value is outside the supported values Oracle allows. You might be thinking, "Where did he come up with a -9999?". If you still have access to 7.3.4, and apply a format mask of MM/DD/SYYYY, it will expose the sign on the year and the fact that Baan uses a negative year for its null date values. Oracle told me that it does not support the Baan null date. Also refer to Baan Solution # 5230 on "the details of the oracle driver parameter ora_date".

Gilbert Guymer
Database Administrator
Lufkin Industries, Inc.

Hi,

Got it. thank you for baan solution #5230 and #1880.

Hi,

Please let me know how to fix the above problem for SQL SERVER 2005