|
Problem IC73893
|
Status: Closed |
DEACTIVATE EVENT MONITOR ON REMOTE NODE COULD LEAVE A STALE/ORPHAN APPLICATION CAUSING QUIESCE DB COMMAND TO HANG. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When a deactivate event monitor on remote node
db2 set event monitor xxxxx state 0
is invoked from the catalog node, it could leave a stale/orphan
application in the remote node.
This orphaned application could cause the quiesce database
command to hang.
Symptom:
1) The application snapshot on the remote node, should have the
"Decoupled" keyword for the Application status field and strange
values of the "Configuration NNAME of client" and "Client
database manager product ID" fields.
Application Snapshot
Application handle = 84104
Application status = Decoupled
Status change time =
Application code page = 819
Application country/region code = 1
DUOW correlation token =
Application name =
Application ID =
Sequence number = 00003
TP Monitor client user ID =
TP Monitor client workstation name =
TP Monitor client application name =
TP Monitor client accounting string =
Connection request start timestamp = 11/22/2010
09:14:09.352715
Connect request completion timestamp = 11/22/2010
09:14:09.353470
Application idle time = 3 days 4 hours 40
minutes 29 seconds
CONNECT Authorization ID =
Client login ID =
Configuration NNAME of client = *
Client database manager product ID = X |+
<There are other strange values on other occurrences of the
problem>
Configuration NNAME of client = *
Client database manager product ID = X ?b+
Configuration NNAME of client = 226*
Client database manager product ID = X
</there might be more strange values>
Process ID of client application = 699
Platform of client application = LINUX
Communication protocol of client = Local Client
Inbound communication address =
Database name = TESTDB
Database path = <TESTDB database
path>
Client database alias = TESTDB
Input database alias = TESTDB
Last reset timestamp =
Snapshot timestamp = 11/25/2010
13:54:38.724761
Coordinating database partition number = 0
Current database partition number = 2
2) if user invokes "db2 quiesce database immediate force
connections" ==> the quiesce cmd will hung |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users using DB2 v97 fp5 prior releases. *
****************************************************************
* PROBLEM DESCRIPTION: *
* DEACTIVATE EVENT MONITOR ON REMOTE NODE COULD LEAVE A *
* STALE/ORPHAN APPLICATION CAUSING QUIESCE DB COMMAND TO *
* HANG. *
****************************************************************
* RECOMMENDATION: *
* Do not deactivate event monitor on remote node explicitly. *
**************************************************************** |
| Local Fix: |
Do not deactivate event monitor on remote node explicitly. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Apply DB2 V97 FP5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.01.2011
12.12.2011
12.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
