This content has been marked as final. Show 3 replies
Is anything broken?
If it is please describe the breakage in detail.
If not ... don't fix it.
Nothing is broken (until now, i never used them and i am not the one who wrote these scripts), however i was wondering why they (on the remote server) are using NLS_LANG = AMERICAN_AMERICA.WE8ISO8859P15 while on the same server the NLS_LANG= AMERICAN_AMERICA.WE8ISO8859P1 ( in .profile).
These scripts where originally used with oracle client v9.2 ( and set NLS_LANG = AMERICAN_AMERICA.WE8ISO8859P15) , oracle client version was upgraded to v10.2 so i thought i should update them and faced the dilemma of NLS_LANG :?
do you think i should leave the NLS_LANG as it is in those scripts ?
Edited by: taha on 12 mars 2012 22:37
Edited by: taha on 13 mars 2012 09:46
Edited by: taha on 3 mai 2012 10:43
NLS_LANG should generally be set to the character set of data that the script operates on. WE8ISO8859P1 is similar to WE8ISO8859P15 but not identical. The main difference is the presence of the Euro currency symbol and a few additional Latin characters (e.g. "oe" ligature) in WE8ISO8859P15. If your scripts process pure 7-bit ASCII data, then NLS_LANG does not really matter (both character sets define the ASCII sub-range identically). But if they process French characters, then you must identify which encoding is the data in. For example, does the data contain the Euro symbol with the code 0xA4, or the "oe" ligature at 0xBD or maybe the "1/2" symbol at 0xBD instead?