Is it ok for me to set the database NLS_CHARACTERSET=UTF8 (UNICODE) and on the workstation we set NLS_LANG=AMERICAN_AMERICA.CL8MSWIN1251, instead of NLS_LANG=AMERICAN_AMERICA.UTF8????
i dont think so.. they must be the same... once, i had experience when my applications and database have different values for nls_lang, and i had to make them the same before doign anythign else..
and of course, i set them to the same value as the database...
also, one of the warnings messaeg is that if i messed up this nls_lang, my database would be corrupted.. i am not sure how this is goign to happen but i am not going to take chances so just changed the value as the database and all is fine..
Originally posted by learning_bee Is it ok for me to set the database NLS_CHARACTERSET=UTF8 (UNICODE) and on the workstation we set NLS_LANG=AMERICAN_AMERICA.CL8MSWIN1251, instead of NLS_LANG=AMERICAN_AMERICA.UTF8????
Hm, I believe, generally speaking, db character set should be able to handle all characters in the applictions,
and client character set determines how you should set nls_lang.
I.e. if app/os/terminal is using "MS code page 1251" you should indicate this to Oracle NLS (Two-Task?) layer by setting NLS_LANG=.CL8MSWIN1251, so that conversion to, say, UTF-8 is done properly. This way, if you have other clients (e.g. ISO 8859-1) they can have the proper characters read back.
Bookmarks