• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1068
  • Last Modified:

ODBC Translation Library

On a Windows client, I ran odbcTst with Oracle's driver version 8.1.6.4
The DB and the NLS_LANG parameters are both WE8ISO8859P1.
When sending a hebrew character it is translated to the hex code of 191 (which is an upside down question mark).
The hebrew characters hexa code is 242.
It does work fine when I'm using English characters.
I can see this by using the ODBC trace facility.
I have 10 othe DBs with the same character set and I can't use any othe char set.


1. Does any one know how to fix this?
2. What is the "Translation Library" and can i be changed?

Thanks
0
peledc
Asked:
peledc
1 Solution
 
forquestionCommented:
SQLNet is used to translate the character between layers. If both databases and clients are using same character set, SQLNet will not translate any character in between. The other issue will be the OS character set and display character set and fonts.

ALso, JDBC thin client can bypass SQLNet translation. If the application is using JDBC OCI, then try JDBC thin client.

0

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now