Main Page | Report this Page
Computers Forum Index  »  Computer - Databases - Oracle (Tools)  »  NLS_LANG...
Page 1 of 1    

NLS_LANG...

Author Message
Gerard H. Pille...
Posted: Wed May 27, 2009 10:17 pm
Guest
Is there any way to determine the NLS_LANG of a client using SQL or PL/SQL.

sys_context('USERENV','LANGUAGE') gives the database characterset, not the clients.

Thanks,

Gerard
 
Maxim Demenko...
Posted: Wed May 27, 2009 10:35 pm
Guest
Gerard H. Pille schrieb:
Quote:
Is there any way to determine the NLS_LANG of a client using SQL or PL/SQL.

sys_context('USERENV','LANGUAGE') gives the database characterset, not
the clients.

Thanks,

Gerard

For local connections ( also using bequeth protocol) you can get the
environment variables with dbms_system.get_env procedure.

Best regards

Maxim

--
Why make things difficult, when it is possible to make them cryptic
and totally illogical, with just a little bit more effort?

Aksel Peter Jørgensen
 
Gerard H. Pille...
Posted: Thu May 28, 2009 12:55 am
Guest
Maxim Demenko schreef:
Quote:
Gerard H. Pille schrieb:
Is there any way to determine the NLS_LANG of a client using SQL or
PL/SQL.

sys_context('USERENV','LANGUAGE') gives the database characterset, not
the clients.

Thanks,

Gerard

For local connections ( also using bequeth protocol) you can get the
environment variables with dbms_system.get_env procedure.

Best regards

Maxim



Alas, we want to check if all PC's have been correctly configured, even all clients.
 
Maxim Demenko...
Posted: Thu May 28, 2009 1:04 am
Guest
Gerard H. Pille schrieb:
Quote:
Maxim Demenko schreef:
Gerard H. Pille schrieb:
Is there any way to determine the NLS_LANG of a client using SQL or
PL/SQL.

sys_context('USERENV','LANGUAGE') gives the database characterset,
not the clients.

Thanks,

Gerard

For local connections ( also using bequeth protocol) you can get the
environment variables with dbms_system.get_env procedure.

Best regards

Maxim



Alas, we want to check if all PC's have been correctly configured, even
all clients.

As far as i know, it can't be done from within the Oracle server.
I guess, it should be done by os means, another difficulty may be in the
term environment *variable*, i.e., it can be changed every time by the
client.

Best regards

Maxim

--
Why make things difficult, when it is possible to make them cryptic
and totally illogical, with just a little bit more effort?

Aksel Peter Jørgensen
 
Gerard H. Pille...
Posted: Thu May 28, 2009 10:18 pm
Guest
Maxim Demenko schreef:
Quote:
Gerard H. Pille schrieb:
Maxim Demenko schreef:
Gerard H. Pille schrieb:
Is there any way to determine the NLS_LANG of a client using SQL or
PL/SQL.

sys_context('USERENV','LANGUAGE') gives the database characterset,
not the clients.

Thanks,

Gerard

For local connections ( also using bequeth protocol) you can get the
environment variables with dbms_system.get_env procedure.

Best regards

Maxim



Alas, we want to check if all PC's have been correctly configured,
even all clients.

As far as i know, it can't be done from within the Oracle server.
I guess, it should be done by os means, another difficulty may be in the
term environment *variable*, i.e., it can be changed every time by the
client.

Best regards

Maxim


Indeed, and we would like to prevent that. A client pretending to use the same character set as
the database, can store quite some rubbish.
 
Frank van Bortel...
Posted: Sun Jun 21, 2009 2:53 pm
Guest
Laurenz Albe wrote:

Quote:
For example:
Both Note 14786.1 and Note 341676.1 agree that code point
hex 0x80 is not assigned in the WE8ISO8859P1 character set.
Yet Oracle will happily accept this byte when you feed it
to the client.

This is what I complain about.


Point taken.
And I can only agree; I wish Oracle only had the options "Single Byte"
and "Multi Byte" when creating a database.

The client side network should warn about using unassigned code points.
However - it would generate a *lot* of warnings!
--

Regards,
Frank van Bortel
 
 
Page 1 of 1    
All times are GMT
The time now is Sat Dec 05, 2009 1:39 pm