ODBC Translation Library

On a Windows client, I ran odbcTst with Oracle's driver version
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?

Who is Participating?
forquestionConnect With a Mentor Commented:
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.