using JDBC not ODBC ,,,
Main Topics
Browse All TopicsWe had this problem when we used bea sybase jdbc driver. We have mutiple weblogic instances running and it only occurs at 2 of them:
[BEA][Sybase JDBC Driver]Transliteration failed, reason: invalid UTF8 data; nested exception is java.sql.SQLException: [BEA][Sybase JDBC Driver]Transliteration failed, reason: invalid UTF8 data..
Anyone knows the reason for the problem and any possible solution?
Thx!!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
JDBC are wire line drivers.
As you point out, the problem cannot be with the database end of things because the problem only occurs on a couple of the WebLogic machines.
I would review the installation guide for WebLogic paying particular attention to any information on character sets or Locales. The O/S may also have a different Locale set; see if the problem boxes are different from the ones that work properly. Finally, go through the JDBC connection strings and data source definitions to see if there is a difference.
You should find the problem by process of elimination. At least you have working examples to compare to.
Regards,
Bill
Business Accounts
Answer for Membership
by: grant300Posted on 2007-07-12 at 07:18:28ID: 19471925
This most likely results ffrom a mismatch in the character set between the databases and the installations of WebLogic. WebLogic is expecting UTF8 characters and is getting something else and choking on it.
The ideal situation is to have everything, database and WebLogic servers, using the same character set so that there is never a need to do translation. The first thing you will want to do is check the character set configuration on your troubled BEA machines and the WebLogic installations. I am guessing that you really want all the WebLogic servers configured the same way anyway.
Barring that, you can set the "Locale" on the Sybase client on the WebLogic servers to match the character set (probably UTF8) that they are using. This assumes that the BEA ODBC drivers use the standard CTlib from Sybase and are not what is called Wire Line.
If the BEA ODBC driver is "Wire Line", (meaning it implements the Sybase client internally) you may be able to set the character set or Locale in the ODBC Data Source configuration.
Check the default character set on your Sybase servers and use that as a starting point to know which way to push the WebLogic installations.
Regards,
Bill