Re: Illegal date format...

Yes It has happened to us too, This happens if you are using the Standard Oracle Adapters. This happens because of the OCI calls that Web Methods is using. There is a work around to it. Let's say you have an integration using Web Methods between two application, App A and App B

A(agent) - Broker -B(agent)

This will happen if you have BrokerDate field in App A as part of the canonical that should go to App B but the date field came as null from by App A. The broker in this case initializes the date field to a date determined by the broker.

In both the above agents wherever there are Date fields use a corresponding indicator variable for the date fields and also put those indicator variable as part of your data copy routine.

This will work and is the only work around.

Thanks
Anand Sharma.

Andrew Allen <ajallen_at_mailhost.det.ameritech.net> wrote in message news:<3D881A68.AE7C9537_at_mailhost.det.ameritech.net>...
> Eddie wrote:
> >
> > I saw it with my own eyes! Webmethods inserted an illegal date into
> > the Oracle database. When I query the table here is what I get. We are
> > running database version 7.3.4. And yes the eta_date_lfdat is a date
> > field in the databse. Has anyone seen this before? Eddie Shuler
> >
> > 1* select to_char(eta_date_lfdat,'dd-mon-yyyy') from sap_delivery
> > SQL> /
> >
> > TO_CHAR(ETA_DATE_LFDAT,'DD-MON-YYYY')
> > ---------------------------------------------------------------------------
> > 00-december-0000
> > 00-december-0000
>
> No you DID NOT!!! the date format you specified in your query
> would have returned 00-DEC-0000. You obviously created this result
> set. Quit wasting our time.
Received on Wed Oct 16 2002 - 11:16:02 CDT