|
Problem IC83108
|
Status: Closed |
LASTUSED DAEMON, DB2LUSED PROCESS, MAY SHUT DOWN UNEXPECTEDLY WHEN THE DATABASE IS QUIESCED. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The LASTUSED daemon, db2lused process, that is used to update
the LASTUSED field in certain system catalogs,
such as syscat.tables, may shut down unexpectedly when a
database is quiesced (either by QUIESCE DATABASE or
QUIESCE INSTANCE) and then unquisced.
The user would notice that the process is no longer around in
the db2pd -edus output even
though the database is active. The following error would be
noticed in the diag:
2012-05-02-19.28.12.640875-240 I10151E594 LEVEL: Error
PID : 5262 TID : 46912954689856PROC :
db2sysc
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-34 APPID: *LOCAL.DB2.120502232733
AUTHID : db2inst1
EDUID : 49 EDUNAME: db2lused (SAMPLE)
FUNCTION: DB2 UDB, database monitor, sqmLastUsedDaemon::main,
probe:20
RETCODE : ZRC=0x870F00B9=-2029059911=SQLO_SEM_TIMEOUT
"Return code from sqlowait when time out value has
been reached"
DATA #1 : String, 31 bytes
Last Used Daemon Shutting Down.
eg.
db2 quiesce db immediate
followed by an
db2 unquiesce db
As the LASTUSED daemon wakes up every 15 mins to gather usage
information, you may notice the problem
approximately 15 mins after the database has been unquiesced and
is active.
db2pd -edus | grep lused
command would show no db2lused process in the list. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Workaround is to Avoid quiescing and unquiescing the *
* instance or database. *
* Or upgrade to 9.7 FP7 or subsequent fix pack *
**************************************************************** |
| Local Fix: |
Avoid quiescing and unquiescing the instance or database. |
| available fix packs: |
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 |
Problem Fixed in DB2 Version 9.7 Fix Pack 7 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC87871
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.05.2012
05.11.2012
05.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP7
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.7
|
 |
