| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2197.1 | different NLS_LANG setting? | UTROP1::16.197.208.129::VISSER_J | Joop Visser @ UTO | Tue Apr 15 1997 09:41 | 20 |
| VMS, nationial char displayed as ? char
+++ Conversion done because of different language setting DB and LNX
Check the language of the database:
type op$root:[servers]dblang.
To force the same language setting for the cell process in
sys$manager:runo17011.com the next line is put first by LinkWorks.
The value is
define NLS_LANG .WE8ISO8859P1
is set as first command. This sets it for the cell deamon process.
You can set it system wide. Add in file: sys$startup:lnx$startup.com
the command:
DEFINE/SYS NLS_LANG .WE8ISO8859P1
Joop Visser,
LinkWorks Exp. centre
|
| 2197.2 | Why has it stopped working? | COPCLU::PETHOMSEN | | Tue Apr 15 1997 12:42 | 30 |
|
reply .1
In the file op$root:[servers]dblang. is the following line:
WE8ISO8859P1
In the file sys$manager:runo17011.com is the line:
$define NLS_LANG .WE8ISO8859P1
When you do af sh log NLS_LANG this logical is not defined.
To me this seems to be like it should be. Therefore I'm a bit confused
why it has suddenly stopped working.
What we have done now is to give the command:
define/sys NLS_LANG .WE8ISO8859P1
and put the same definition in the sys$startup:lnx$startup.com
We will se what happens when the next user logs in and after a start
and stop of linkworks.
Regards
Poul Erik Thomsen
|
| 2197.3 | It did not help! | COPCLU::PETHOMSEN | | Thu Apr 24 1997 16:20 | 12 |
| Hello
Unfortunately these things did not help. Linkworks has been stopped and
started. We have defined the global logical name.
I'm wondering whether there is a file that contains the list of
international characters and that this file is not there anymore?
Regards
Poul Erik Thomsen
|
| 2197.4 | | elec1.uto.dec.com::wijermars_v | | Mon Apr 28 1997 10:58 | 16 |
| Hi,
Perhaps Oracle has such tables, but I would not know where to look for them.
Characters are converted when data is exchanges between the operating system and the database.
This is done based on the character set defined in the database and the nls_lang logical set on
the operating system.
When menu-items etc are incorrect, the nls-lang setting is wrong for the cm/am processes.
When this is the case, it does not help setting the logical correct as the cache contents on the
server will be wrong. You would have to clean-up the cache on the server then.
When names of objects etc are wrong, setting the logical would fix the problem.
If this is not the case you might check if the logical name table is not full
The size is determined by the jtquota.
As the cells are detached processes, you would have to check the sysgen parameter pql_djtquota.
Vincent
|