Murray, Laura (US)
Laura.Murray at am.jll.com
Tue Jul 29 14:11:59 EDT 2008
Still troubleshooting the problem with Japanese Characters getting
garbled upon transmission from Oracle db to SQL Server db using freetds
.64 and unixodbc 2.2.12.
My colleauge found this suggestion...what do you think?:
"Please try to change FreeTDS's client char set setting from UTF-8 to
EUCJP-MS as below.
1) add code EUCJP-MS to 'src/tds/encodings.h'.
2) change strings buffer from 256 to 100000 in 'src/tds/write.c'.
3) modify freetds.conf as such: client charset=EUCJP-MS
I implemented 2) and 3) but for 1) did not know where to put the code in
the file. Also, just wanted to know if you approve of this approach, in
general. If so.....after these modifications, do I need to redo the
freetds "make" and "make install"?
From: freetds-bounces at lists.ibiblio.org
[mailto:freetds-bounces at lists.ibiblio.org] On Behalf Of James K. Lowden
Sent: Friday, July 25, 2008 8:07 AM
To: FreeTDS Development Group
Subject: Re: [freetds] unicode
Murray, Laura (US) wrote:
> I also tried some settings in freetds.conf to get a log file....but
> still no log file:
> host = xx.xx.x.xx <---didn't want to post our ip....:)
> port = 1433
> tds version = 8.0
> client charset = UTF-8
> dump file = /opt/oracle/odbc/etc/freetds.log
> debug level = 10
> dump file append = yes
Both alternatives work. If you use TDSDUMP, the variable must exist in
the environment of the process running the FreeTDS library. I can
that would be a little tricky with your setup.
If you use the "dump file" property of freetds.conf, be sure you're
an ODBC-Combined configuration. (I assume your gateway relies on ODBC.)
If you don't specify the server using the "Servername" connection
attribute, freetds.conf will not be consulted and the dump file will not
FreeTDS mailing list
FreeTDS at lists.ibiblio.org
This email is for the use of the intended recipient(s) only. If you have
received this email in error, please notify the sender immediately and then
delete it. If you are not the intended recipient, you must not keep, use,
disclose, copy or distribute this email without the author's prior
permission. We have taken precautions to minimize the risk of transmitting
software viruses, but we advise you to carry out your own virus checks on
any attachment to this message. We cannot accept liability for any loss
or damage caused by software viruses. The information contained in this
communication may be confidential and may be subject to the attorney-client
privilege. If you are the intended recipient and you do not wish to receive
similar electronic messages from us in the future then please respond to the
sender to this effect.
More information about the FreeTDS