> What could be the possible reasons for this?
It is a charset problem. You need to define the correct charset to be used with Sybase.
Main Topics
Browse All TopicsI try to connect to a Sybase server from my machine.
When I do a direct connection from Java, I am able to connect to the Sybase server.
Also, when i configure it as a ODBC connection, and try to do a Test Connection, the result is successful.
But, when i try to configure it as a Datasource in WAS server, i am getting the error message " java.sql.SQLException: JZ00L: Login failed. Examine the SQLWarnings chained to this exception for the reason(s)."
My WAS version is 6.1.
What could be the possible reasons for this?
I checked my user id and password supplied to WAS and it is correct.
My question is, when I am able to connect through ODBC, why am I not able to connect to the Sybase sever as a Datasource from WAS?
Please help me out....
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.
Business Accounts
Answer for Membership
by: grant300Posted on 2008-04-07 at 08:15:21ID: 21297712
I don't suppose you were able to "Examine the SQLWarnings chained to this exception..."?
There are a number of reasons this could be happening:
- You could have a classpath problem
- You could have a path and/or environment variable problem in the context in which Websphere runs. If it cannot find all the Sybase connection components it needs, it will barf.
- You may have something wrong in the connection setup info in WAS.
My vote is for number two; you are missing path and/or other required Sybase environment variables. You should take a look at the startup script for WAS and make certain it is sourcing the Sybase env.sh or equivalent script. This sets the necessary environment variables so that the client components of Sybase (ct-lib) can find each other.
Regards,
Bill