Re: Problem with TO_CHAR(timestamp, 'DD.MM.YYYY HH24:MI') --> ORA-01722

Dear oracle-users,

you are so right! I was stupid, to forget controlling the table-definition!
The timestamp-field was defined as as varchar2. Sometimes the oracle-schema-manager from the 7.4.3-Client-Version plays something strange...

Thank you for answering so quickly!

Peter

"JustAnotherDBA" <burttemp1REMOVE_THIS_at_bellsouth.net> wrote in message news:<YJDxa.68463$dc5.62162_at_fe09.atl2.webusenet.com>...
> The timestamp column is probably defined as a varchar2 .
>
> --
>
> "Peter Elsen" <p.elsen_at_kreis-dueren.de> wrote in message
> news:955858ba.0305170210.51742686_at_posting.google.com...
> > Hello,
> >
> > my Internet-Provider has changed the Oracle DB to Version 8.1.7.
> > Since this update I got an ORA-01722-Error when using this statement:
> >
> > SELECT TO_CHAR(timestamp, 'DD.MM.YYYY HH24:MI') FROM UMFRAGE;
> > --> ORA-01722: Ungültige Zahl [= invalid number]
> >
> > The datefield 'timestamp' contains a trigger-generated SYSDATE.
> >
> > I tried to use TO_DATE(...) instead of TO_CHAR: I resolve only Day,
> > Month and Year, but no time-information (hours and minutes).
> >
> > What can I do to resolve the complete date- and timeinformation ?
> >
> > Thank You!
> >
> > Peter
Received on Mon May 19 2003 - 00:32:32 CDT