Home » SQL & PL/SQL » Client Tools » char differences between SQL+ and SQL developer
char differences between SQL+ and SQL developer [message #596307] Fri, 20 September 2013 03:17 Go to next message
amauri
Messages: 18
Registered: May 2013
Location: Italy
Junior Member
Hi,

we have an issue on a server, where if we insert a value containing foreign characters from SQL+ we see it screwed up from SQLdev, whereas if we do the same insert from SQLdev it's then screwed up in SQL+.
All operations are performed on the DB server itself, SQLdev connection type is TNS and the entry being used is the same as the one used by SQL+.
We checked v$nls_parameters and the values contained there are the same from both SQL+ and SQLdev.
any ideas?

Alberto
Re: char differences between SQL+ and SQL developer [message #596309 is a reply to message #596307] Fri, 20 September 2013 03:24 Go to previous messageGo to next message
dariyoosh
Messages: 536
Registered: March 2009
Location: Iran / France
Senior Member
Hi,

Well, just saying "we see it screwed up" doesn't give much information about the problem, but maybe the same (or similar) question has already been answered:

http://www.orafaq.com/forum/mv/msg/189560/596260/#msg_596260

Regards,
Dariyoosh
icon10.gif  Re: char differences between SQL+ and SQL developer [message #596310 is a reply to message #596307] Fri, 20 September 2013 03:24 Go to previous messageGo to next message
Michel Cadot
Messages: 59803
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

NLS_LANG (especially NLS_CHARACTERSET) are not the same ones; this is something you cannot check with v$nls_parameter.

Re: char differences between SQL+ and SQL developer [message #596311 is a reply to message #596310] Fri, 20 September 2013 03:27 Go to previous messageGo to next message
amauri
Messages: 18
Registered: May 2013
Location: Italy
Junior Member
Hi Michel, where do I check NLS_LANG settings in SQL+ and SQL dev.?
Re: char differences between SQL+ and SQL developer [message #596312 is a reply to message #596311] Fri, 20 September 2013 03:32 Go to previous messageGo to next message
dariyoosh
Messages: 536
Registered: March 2009
Location: Iran / France
Senior Member
NLS_LANG is normally defined as an OS level environment variable.

Regards,
Dariyoosh
Re: char differences between SQL+ and SQL developer [message #596313 is a reply to message #596311] Fri, 20 September 2013 03:32 Go to previous messageGo to next message
amauri
Messages: 18
Registered: May 2013
Location: Italy
Junior Member
Sample
insert in SQL+:
insert into MyTable(MyWord)values('federaçao');
select from SQL+:
select MyWord from MyTable;
MyWord
------------
federaçao
select from SQL developer:
select MyWord from MyTable;
MyWord
------------
federa│ao
Re: char differences between SQL+ and SQL developer [message #596314 is a reply to message #596313] Fri, 20 September 2013 03:35 Go to previous messageGo to next message
amauri
Messages: 18
Registered: May 2013
Location: Italy
Junior Member
Hi dariyoosh,

the server does not have it set in the environment, but it's set in the registry.
Re: char differences between SQL+ and SQL developer [message #596315 is a reply to message #596313] Fri, 20 September 2013 03:38 Go to previous message
dariyoosh
Messages: 536
Registered: March 2009
Location: Iran / France
Senior Member
So the 'ç' character seems to be the source of the problem, that's why you should check your nls_lang and the characterset on the server.

Quote:
the server does not have it set in the environment, but it's set in the registry

Have a look at this:

Configuring Locale and Character Sets Using NLS_LANG

What is the value of NLS_LANG that you have defined for your OS (Windows I may assume?)

Regards,
Dariyoosh

[Updated on: Fri, 20 September 2013 03:39]

Report message to a moderator

Previous Topic: how to run all sql scripts from one script
Next Topic: ORA-12504, TNS:listener was not given the SID in CONNECT_DATA
Goto Forum:
  


Current Time: Thu Nov 27 04:03:53 CST 2014

Total time taken to generate the page: 0.19666 seconds