By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,905 Members | 894 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,905 IT Pros & Developers. It's quick & easy.

DB2 Type 4 JDBC Driver - Support for passwords with "|"

P: n/a
Hi,

I am using the DB2 Type 4 JDBC Driver to connect to my DB2 8.2 for
Windows server. Everything works perfectly unless I have a password
with the pipe character ( "|" ) in it. The server password has a "|"
character in it. If I do this, I get an exception stating that the
password is invalid.

This is what I execute ...

String password = "password|";
Connection conn = DriverManager.getConnection(url, "username",
password);

And this is the exception that I get ...

com.ibm.db2.jcc.b.SqlException: Connection authorization failure
occurred. Reason: password invalid.

The major and minor versions of the driver are 2.6. I can't seem to
find any other references on the web on this issue. Is this a known
limitation with the JDBC driver?

-Niels

Feb 2 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
aj
Interesting. I found the same behavior, but for an
exclamation point.

http://groups.google.com/group/comp....00c4aaae5bf616

The only solution I found: change your password.

aj

ni*******@gmail.com wrote:
Hi,

I am using the DB2 Type 4 JDBC Driver to connect to my DB2 8.2 for
Windows server. Everything works perfectly unless I have a password
with the pipe character ( "|" ) in it. The server password has a "|"
character in it. If I do this, I get an exception stating that the
password is invalid.

This is what I execute ...

String password = "password|";
Connection conn = DriverManager.getConnection(url, "username",
password);

And this is the exception that I get ...

com.ibm.db2.jcc.b.SqlException: Connection authorization failure
occurred. Reason: password invalid.

The major and minor versions of the driver are 2.6. I can't seem to
find any other references on the web on this issue. Is this a known
limitation with the JDBC driver?

-Niels

Feb 2 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.