Re: NLS with 8i(8.1.7) Solaris - Help

Alex Filonov wrote:
>
> Dirk Kiehne wrote:
>
> > Dirk Kiehne wrote:
> > >
> > > Hi,
> > >
> > > I didn't think we were having problems with our Asian Language
> > > DBs since I was careful to set NLS_LANG and ORA_NLS33 in my
> > > environment as well as select the right characterset during
> > > DB creation in dbassist.
> > >
> > > I find however, that after querying nls_database_parameters
> > > that I have:
> > >
> > > NLS_LANGUAGE AMERICAN (Should be KOREAN)
> > > NLS_TERRITORY AMERICA (Should be KOREA)
> > > NLS_CHARACTERSET KO16MSWIN949 (Incorrect)
> > >
> > > NLS_NCHAR_CHARACTERSET KO16KSC5601 (Correct)
> > >
> > > I have a few questions that I hope someone will be able to help
> > > with:
> > >
> > > Do I need to explicitly set NLS_LANGUAGE, NLS_TERRITORY
> > > and NLS_CHARACTERSET in initORCL.ora, even though they were
> > > set in the environment and during DB creation ?
> > >
> > > The client data (Korean Windows machine) is apparently using
> > > KO16MSWIN949. Can this be forced into KO16KSC5601, which I
> > > used to create the DB ?
> > >
> > > Does the 8.1.7.1b patch address some of these issues if this
> > > is not my problem ?
> > >
> > > Using jdbc thin driver to put data into the DB, do we set
> > > the environment variables for jdbc, since we go from Windows
> > > machine to server(jdbc thin) to Oracle ?
> > >
> > > Thanks for any insight.
> > > -Dirk
> >
> > OK, I've solved part of the issues. It appears that someone
> > (read developer) changed one of the 'CHARACTERSET' variables.
> > I've recreated the DB with both set to the same thing now.
> >
> > I still get NLS_LANGUAGE and NLS_TERRITORY set to AMERICAN
> > and AMERICA even though they are set to KOREAN and KOREA
> > in my environment variables. I tried to set them explicitly
> > in initORCL.ora but a query of nls_database_parameters still
> > shows AM... (???)
> >
> > Any help greatly appreciated.
> > -Dirk
>
> Don't mind nls_language and nls_territory in server settings, they don't
> mean anything. The main thing is what do you have on client.
> NLS_LANGUAGE defines language of messages, NLS_TERRITORY defines date
> and numeric format. I think you are OK. Don't know about jdbc though,
> didn't try NLS charset conversion with it. And you need it, because you
> charsets on client and server are different.

Thanks for the response,
After doing several frantic searches on technet I found the tables nls_database_parameters, nls_session_parameters and nls_instance_parameters.

It seems that nls_session_parameters are the important ones. I don't know what's wrong with the nls_database_paramters.

I also did a search on jdbc and nls and found the programming guidelines for both thin and thick drivers. We'll have to change a few things. -Dirk Received on Wed Aug 29 2001 - 11:56:53 CDT