Re: TO_CHAR bug?

suvinay wrote:
> Thanks for all the feedback.
> Dave, you are correct about "split and concat" - that works. I didnot
> know about the
> length restriction of dataformat. Not sure if that was causing it but
> here is a little bit
> more information.
>
> If it was 24 char limit issue, then why does it work if the SQL
> statement looks as follows:
>
> select TO_CHAR(systimestamp, 'YYYY-MM-DD"T"HH24:MI:SS.FF2"Z "') from
> dual;
>
> Notice two space inside "Z " i.e, "Z<space><space>". This produces
> correct result.
> So apparently it is truncating last two characters which to me
> indicates that it is
> something to do with character set issue since TO_CHAR's behavior
> depends
> on db character set.
>
> So looking at current character set of db, this is what I have:
>
> CHARACTER SET UTF8
> NATIONAL CHARACTER SET AL16UTF16
>
> and the problem shows.
>
> I recreate the db with the following character sets:
>
> CHARACTER SET WE8ISO8859P1
> NATIONAL CHARACTER SET UTF8
>
> and the problem is gone! woohooo!
>
> So definitely a character set issue.
>
>
> BTW, this is 9206 ORACLE.
>
>
>
> Thanks
> -- suvinay

--snip--

Yes it appears to be the Bug 4777057
WRONG OUTPUT TO_CHAR(DATE FORMAT) IN UTF8 DATABASE I don't see any workaround listed in the bug description

Anurag Received on Tue Jul 25 2006 - 12:27:12 CDT