 |
 |
Archives of the TeradataForum
Message Posted: Mon, 25 Oct 2004 @ 09:14:47 GMT
| Subj: | | Re: Changing the default client character set |
| |
| From: | | Victor Sokovin |
Satya,
| | The defaultcharcterset set in the Create User is one among the following values. | |
| | UNICODE, KANJI1, KANJISJIS, GRAPHIC and ASCII for Teradata on WINDOWs machine. | |
| | But the client character sets are KANJIEUC_0U, HANGULKSC5601_2R4, etc., | |
User and client levels are different indeed in this respect. On the client, you need to have physically the possibility to use different
character sets. For example, specific fonts, code pages and encodings must be installed and supported by the client OS. Because so many different
encodings and code pages exist, the client-side specifications must be much more detailed than the database settings, and that's exactly the
difference you have observed. TD does not support each and every encoding you find on the market so you have to check which ones are supported for
your language and present the options to the customers. If they are happy with one encoding you can start with it and "map" your "logical"
database level charset to that specific technical implementation on the client, and test the settings with both import and export of data to /
from the database.
There is also an option to specify your own charset.
| | please eplain more on the following | |
| | "1. Application / utility specific explicit commands (you can add them to standard scripts)."' | |
Practically each client utility connecting to the database is aware of the character sets these days. CLI, BTEQ, MultiLoad, FastExport etc.
However, the syntax may differ per utility. It is best to check in the user manuals for the utilities you use. Just to name an example, in BTEQ or
FastLoad, you say
.SET SESSION CHARSET ;
Again, not all charsets may be supported by a particular utility so consulting the latest manual seems to be a good idea before further
planning.
| | As a user I donot have the permission to modify the dbc.hosts info table. But I can retreive the value set in that. | |
I thought you said you had set the server to Kanji so I assumed you were on the DBA side.
| | I cannot modify the clispb.dat file at run time thru a program from where I get the client character set. | |
In my opinion, clispb.dat is meant for permanent settings typically in use by the client. For the run time changes try the session level
commands mentioned above. They will override the clispb.dat settings. Differences between client and user levels apply here.
Regards,
Victor
| |
