|
Problem IC83679
|
Status: Closed |
AFTER AN APPLICATION IS FORCED ON A WINDOWS DATABASE SERVER, THE CLIENT PROGRAM HANGS. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
If an application on a Windows database server is forced, the
client program for that application hangs next time it runs a
query.
This problem does not happen for database servers on any
platform other than Windows.
Here are steps which reproduce the problem:
On the database client, connect to a database that is on a
Windows database server.
For example, run:
db2 "connect to <database> ..."
(substituting for <database> the name of the database on a
Windows database server)
On the Windows database server, force the application.
For example, run:
db2 "list applications"
db2 "force application (<app-handle>)"
(subsituting for <app-handle> the application handle that was
output by "list applications")
On the database client, using the client program for the
application that you forced, run any SQL statement.
For example, run:
db2 "select count(*) from syscat.tables"
At this point the client program ought to get error:
"SQL30081N A communication error has been detected."
But because of this defect it hangs instead.
Now if you stop the stop the DB2 instance on the Windows
database server the client program is no longer hung but gets
the error:
"SQL30081N A communication error has been detected." |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users who connect to a DB2 on Windows database *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* . *
**************************************************************** |
| Local Fix: |
As a workaround to prevent the client program from hanging
indefinitely, you can set
the DB2 registry variable DB2TCP_CLIENT_RCVTIMEOUT on the
database client to the number of seconds that the client program
should wait before it gets the SQL30081N error. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 10.1 Fix Pack 1.
At a minimum, this fix should be applied on the database server. |
| Workaround |
As a workaround to prevent the client program from hanging
indefinitely, you can set the DB2 registry variable
DB2TCP_CLIENT_RCVTIMEOUT on the database client to the number of
seconds that the client program should wait before it gets the
SQL30081N error. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.05.2012
05.11.2012
05.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
