Leap Year Issues?
Posted in 1999
Topics: Platform-Specific Issues
Hello, Has anyone heard of any leap year issues with either the SE or IDS servers. Is so, can anyone direct me as to how to solve these issues ( upgrading servers ... etc ). We currently use INFORMIX-SE 7.24 and INFORMIX-ONLINE-DYNAMICE-SERVER 7.30 on Linux OS. Thanks in advance, Lloyd AJ Wilson
Go to the http://www.informix.com and click on the Year 2000 link on the left side of the page. It will refer you to a page that will contain the Year 2000 issues for each product. Take care. =============================================== Clifton M. Bean cmbean@msn.com SAP/Informix Database Administrator Informix Certified Database Specialist Informix 4GL-Certified Informix D4GL-Certified Tekmetrics Certified Informix DBA Tekmetrics Certified RDBMS Developer =============================================== Lloyd AJ Wilson <lajwilson@sympatico.ca> wrote in message news:01beea61$a1a49e00$e237bfce@wilsonl.harriscomputer.com... > Hello, > > Has anyone heard of any leap year issues with either the SE or IDS servers. > Is so, can anyone direct me as to how to solve these issues ( upgrading > servers ... etc ). We currently use INFORMIX-SE 7.24 and > INFORMIX-ONLINE-DYNAMICE-SERVER 7.30 on Linux OS. > > Thanks in advance, > > Lloyd AJ Wilson
I just finished my Y2K testing (IDS version 7.22.UC3 and SE 7.23.UC1). Everything worked fine until we got to the Leap year date 2/29/00. I set the environmental variable DBCENTURY=C. When trying to convert the string '022900' using the date function (date('022900')) I received error -1204: Invalid year in date. If I try and convert from the string '02292000', it works fine. Informix support has informed me that it is a known bug (I belive #60150) that is related to DBCENTURY and two character representations of the year. An upgrade will fix the problem. All other dates seemed to work fine.