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

Error establishing simultaneous DB connections in UDB 8.1.

P: n/a
Environment: DB2 8.1.4; Windows 2000

We are evaluating the feasibility of upgrading our production DB from
7.2 to 8.1. During this process we've encountered an error when
starting our application program, which establishes several JDBC
connections to the database. However, this problem can be reproduced
in a variety of ways, including using the CLP. Here are the steps
required to reproduce the problem using the command-line processor:

1) Ensure that the DB is running on the server.
2) Open the first instance of the command-line processor on the
server.
3) Open a second instance of the command-line processor on the
server.
4) Enter the following text into each of the command-line processor
instances, WITHOUT pressing enter:
connect to <database> user <username> using <password>
5) Hit the enter key on the first CLP and then quickly hit enter in
the second CLP instance.

In most cases, one or both of the CLP instances will display the
following error:

SQL30082N Attempt to establish connection failed with security reason
"24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001

This error only occurs when attempting to establish simultaneous
connections. If we instead establish one connection in the first CLP
and then establish the second connection in the second CLP instance,
everything works fine.

We have had no such problem with DB27.2. Has anyone else experienced
this problem in 8.1.X? We've been unable to find any related APARs.
Is there a configuration setting that we're missing that will
alleviate this problem?
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
We are on 7.2 EEE AIX and we are often making several virtual
simultaneous connections to DB2 and we get a similar error which is
[IBM][CLI Driver] SQL1403N The username and/or password supplied is
incorrect. SQLSTATE=08004. This doesn't happen all the time and is
very hard to reproduce. We resubmit our job that makes the connection
and it works perfectly the next time. We were never able to figure
this issue out and it still happens occasionally. We never were able
to even come up with a pattern which you apparently have and it sounds
as if maybe this issue is amplified in 8.1.
Spencer Tabbert
se********@hotmail.com (Semaj) wrote in message news:<e4************************@posting.google.co m>...
Environment: DB2 8.1.4; Windows 2000

We are evaluating the feasibility of upgrading our production DB from
7.2 to 8.1. During this process we've encountered an error when
starting our application program, which establishes several JDBC
connections to the database. However, this problem can be reproduced
in a variety of ways, including using the CLP. Here are the steps
required to reproduce the problem using the command-line processor:

1) Ensure that the DB is running on the server.
2) Open the first instance of the command-line processor on the
server.
3) Open a second instance of the command-line processor on the
server.
4) Enter the following text into each of the command-line processor
instances, WITHOUT pressing enter:
connect to <database> user <username> using <password>
5) Hit the enter key on the first CLP and then quickly hit enter in
the second CLP instance.

In most cases, one or both of the CLP instances will display the
following error:

SQL30082N Attempt to establish connection failed with security reason
"24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001

This error only occurs when attempting to establish simultaneous
connections. If we instead establish one connection in the first CLP
and then establish the second connection in the second CLP instance,
everything works fine.

We have had no such problem with DB27.2. Has anyone else experienced
this problem in 8.1.X? We've been unable to find any related APARs.
Is there a configuration setting that we're missing that will
alleviate this problem?

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.