 |
 |
Archives of the TeradataForum
Message Posted: Thu, 28 Jul 2005 @ 15:45:16 GMT
| Subj: | | Re: Unicode setting in ODBC |
| |
| From: | | Victor Sokovin |
| | As far as I am aware 'UNICODE' is not a valid character set name for the ODBC driver. | |
| | Prior to ODBC 3.4 (TTU 8.0) and Teradata V2R6 the only Unicode session character set available in ODBC was 'UTF8'. | |
| | In 3.4 they added 'UTF16'. | |
Just a guess: it could be a user-defined character set, in which case it could be anything.
But whatever it might be it is interesting that the first session can help the second one accept this character set. I mentioned earlier a
possible registry change. On the second thought, I would not exclude a change in the environment variables either. Perhaps this is even more
likely. It would be interesting if the OP could compare the outputs of the SET command (from the Win command line) before and after running the
first session.
Regards,
Victor
| |
