|
Problem IC72746
|
Status: Closed |
THE APPL_STATUS FOR LASTUSED DAEMON MAY BE STICKING IN UOW EXECUTING. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The appl_status monitor element for lastused daemon (db2lused)
is sticking in 'UOW Executing' if db2lused have waited on a lock
to update system catalog. The monitor element shows incorrect
state because db2lused actually do commits in every intervals.
The following steps illustrates one of the scenario to cause
this problem.
1. Update a user table, then take Z lock on the table
2. Wait for more than 15 minutes so that db2lused can update
system catalogs.
3. Print appl_status
$ db2 list application show detail
Application Name Appl. Status DB Name
Handle
------------------- ------- --------------- ---------
db2lused 11 UOW Executing SAMPLE |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users. *
****************************************************************
* PROBLEM DESCRIPTION: *
* The appl_status monitor element for lastused daemon *
* (db2lused) is sticking in 'UOW Executing' if db2lused have *
* waited on a lock to update system catalog. The monitor *
* element shows incorrect state because db2lused actually do *
* commits in every intervals. *
* *
* The following steps illustrates one of the scenario to cause *
* this problem. *
* *
* 1. Update a user table, then take Z lock on the table. *
* 2. Wait for more than 15 minutes so that db2lused can update *
* system catalogs. *
* 3. Print appl_status. *
* $ db2 list application show detail *
* Application Name Appl. Status DB Name *
* Handle *
* ------------------- ------- --------------- --------- *
* db2lused 11 UOW Executing SAMPLE *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to DB2 v9.7 fixpack 4 or later. *
**************************************************************** |
| Local Fix: |
None, users can ignore the application status. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 |
This problem is first fixed in DB2 v9.7 fixpack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.11.2010
19.05.2011
19.05.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
