Solved

ODBC Translation Library

Posted on 2001-07-04
1
1,042 Views
Last Modified: 2007-12-19
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
Comment
Question by:peledc
1 Comment
 
LVL 1

Accepted Solution

by:
forquestion earned 300 total points
ID: 6255424
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

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Note: this article covers simple compression. Oracle introduced in version 11g release 2 a new feature called Advanced Compression which is not covered here. General principle of Oracle compression Oracle compression is a way of reducing the d…
From implementing a password expiration date, to datatype conversions and file export options, these are some useful settings I've found in Jasper Server.
This video shows setup options and the basic steps and syntax for duplicating (cloning) a database from one instance to another. Examples are given for duplicating to the same machine and to different machines
Via a live example, show how to restore a database from backup after a simulated disk failure using RMAN.

911 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now