Re: upper bug?

"Roman Mirzaitov" <rmirzaitov_at_kt.kg> wrote in message news:<absir7$jssat$1_at_ID-127142.news.dfncis.de>...
> Hi,
>
> what character set are you using? Isn't it 7-bit charset?
> I've just checked it with my 8-bit charset - works quite fine. (Oracle 8.1.7
> on Solaris)
>
> Regards,
> --
> Roman Mirzaitov
> Brainbench MVP for Oracle Administration
> www.brainbench.com
>
>
> "Richard Kuhler" <noone_at_nowhere.com> wrote in message
> news:poiE8.1404$DF2.385508_at_twister.socal.rr.com...
> > Why does the Oracle UPPER function convert ascii 128-255 into ascii
> > 0-127?
> >
> > > select ascii(upper(chr(128))) from dual;
> >
> > ASCII(UPPER(CHR(128)))
> > ----------------------
> > 0
> >
> > > select ascii(upper(chr(180))) from dual;
> >
> > ASCII(UPPER(CHR(180)))
> > ----------------------
> > 52
> >
> > > select ascii(upper(chr(255))) from dual;
> >
> > ASCII(UPPER(CHR(255)))
> > ----------------------
> > 127
> >
> >
> > Is there a way to fix this? Note: NLS_UPPER does the same thing.
> >
> >
> > Thanks,
> > Richard
> >

Richard, it might help if you listed the values of v$nls_parameters so viewers could see how you system is set up.

UT1> col parameter format a25
UT1> col value format a40
UT1> select * from v$nls_parameters;

PARAMETER                 VALUE
------------------------- ----------------------------------------
NLS_LANGUAGE              AMERICAN
NLS_TERRITORY             AMERICA
NLS_CURRENCY              $
NLS_ISO_CURRENCY          AMERICA
NLS_NUMERIC_CHARACTERS    .,
NLS_CALENDAR              GREGORIAN
NLS_DATE_FORMAT           DD-MON-RR

HTH -- Mark D Powell -- Received on Wed May 15 2002 - 08:22:17 CDT