Problems with forreign charaters

[Jonas Malmsten]

I have problems reading and writing language specific characters (Swedish aa ae o, german u etc). We have an Oracle 8 server running on a unix box and a web application (storyserver/tcl based) that writes data into some tables, long and varchar2 fields.

We also have an administrative tool written in Delphi using DOA 3.3. I can't get it to read or write the same forreign characters as the web application.

I have managed to read varchar2 fields and get it right by doing an ascii dump of the field like this:

select dump(text) from mytable;

and then having a snippet in delphi do a conversion like:

s := '';
for i := 1 to NumbersInDumpText do
s := s + chr(StrToInt(OneNumberInDumpedText));

//Jonas

 

[Marco Kalter]

You should probably check the following:

• The character set part of the HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\NLS_LANG registry key on your Windows Client where the DOA application runs.
  
• The same for the NLS_LANG registry key or environment variable for the web application.
  
• The character set that the database was created with.

You should find some inconsistencies here.

------------------
Marco Kalter
Allround Automations

 

[Jonas Malmsten]

Setting the registry key to values taken from v_$nls_parameters did the trick

Thanks!

 

[aporto]

I seem to be having a related similar problem with Japanese character sets. I am viewing :

 

[Marco Kalter]

Is the database created with the JA16SJIS character set? If so, do the controls that display these

 

[Todd Rimes]

Hi:

I'm using Oracle 9i and PL/SQL Developer 5.1.1.672. Can someone point me toward a comprehensive checklist for getting Oracle AND PL/SQL Developer to talk Japanese to each other?

Thanks!
Todd Rimes
trimes@sonypictures.com

 

[Marco Kalter]

• Set your Windows locale to Japanese
• Ensure that your database is created with a character set that supports Japanese
• Ensure that the NLS_LANG key of your Primary Oracle Home includes a character set that supports Japanese

 

[Todd Rimes]

Thanks, I'll try this!

Originally posted by Marco Kalter:

• Set your Windows locale to Japanese
• Ensure that your database is created with a character set that supports Japanese
• Ensure that the NLS_LANG key of your Primary Oracle Home includes a character set that supports Japanese

 

[Todd Rimes]

[Deleted]

 

[Todd Rimes]

OKAY:

My DBA says the database was created like this:

• NLS_LANG=AMERICAN_AMERICA.JA16SJIS, which supports the japanese
• DB characterset= UTF8 which supports the multi byte character set.
• You need to set the Client accordingly to view the Japanese characters.

Does that mean I should set NLS_LANG in my ORACLE_HOME.NLS_LANG registry key to be "AMERICAN_AMERICA.JA16SJIS" as well?

Thanks,
Todd

Originally posted by Todd Rimes:
Thanks, I'll try this!

quote:Originally posted by Marco Kalter:

• Set your Windows locale to Japanese
• Ensure that your database is created with a character set that supports Japanese
• Ensure that the NLS_LANG key of your Primary Oracle Home includes a character set that supports Japanese

 

[Marco Kalter]

Does that mean I should set NLS_LANG in my ORACLE_HOME.NLS_LANG registry key to be "AMERICAN_AMERICA.JA16SJIS" as well?

Yes, otherwise Oracle Net will convert the characters between the 2 different character sets.