Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Problems with Oracle 8.1.7 under UNITED LINUX (SuSE 8.1)
"Harald Maier" <maierh_at_myself.com> schrieb im Newsbeitrag
news:m33cfxiylu.fsf_at_ate.maierh...
> Harald Maier <maierh_at_myself.com> writes:
>
> > "Markus Hoss" <ho_at_gruen-ag.de> writes:
> >
> >> Thatīs the way i did it. I made a custom database, selected
> >> WE8ISO8859P15 as characterset and set national charactercode to UTF8
> >> assumig to use unicode. I added the nls_territory, nls_language and
> >> nls_sort parameters set to GERMAN to the init files of the
> >> databases. In the enterprise manager these parameters are shown as
> >> set on GERMAN . If I use the sql statement: select * from
> >> nls_database_parameters I get AMERICAN. Switiching to : select *
> >> from nls_instance_parameters I get GERMAN. Never the less queries
> >> with german umlauten donīt work correctly. Select names > 'Müller'
> >> drops names starting with 'mu' etc.
> >
> > I don't know from which client you try this. If you use the sqlplus
> > tool then it expects in that case that the NLS_LANG variable is set.
> > If not then I assume it uses US7ASCII. Other programs that are linked
> > with the OCI lib do not need this. I don't know.
Itīs the Windows ORACLE client 8.1.7 software under german win2000 sp3. Starting Enterprise Manager and then sqlplus Worksheet. Same directly under Linux. So if its using US7ASCII why the procedure with dbassist?
>
> UUps, did again a test. Other programs that are linked with the OCI
> lib behave the same as sqlplus. I always set the NLS_LANG variable in
> the Client context.
>
> Harald
Thx
Markus
Received on Tue Aug 19 2003 - 08:15:54 CDT