Prev: Making DB2 be I/O aggressive
Next: Whitepaper on Location Intelligence
From: Troels Arvin on 3 Mar 2010 04:51
Hello,

Setup: 9.7.1 (64 bit) running on x86_64 Red Hat Enterprise Linux 5.4.

Often, when I take look at the list of applications, I see a session with
application name "db2lused" in a state of "UOW Executing". Example:
http://troels.arvin.dk/db/db2/db2lused/db2lused.txt

Google is rather silent about db2lused. Only hit is at ftp://
public.dhe.ibm.com/ps/products/db2/info/vr97/pdf/en_US/
DB2PerfTuneTroubleshoot-db2d3e971.pdf which states:
db2lused, for updating object usage

The application doesn't seem to cause any harm (such as CPU or I/O
usage), but I find it strage that it's running so often and for so long.
Should I be worried? Is it an expected scenario?

--
Troels
From: blazer462 on 5 Mar 2010 08:08
This updates the last used status for tables and indexes. When a table/
indexe is used, the lastused column in the syscat.tables/
syscat.indexes is updated with the time when the table/index is used
for the last time. In that way, you can identify the indexes/tables
which are not used for long time and drop them to reclaim the space.


Check this out

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.admin.mon.doc/doc/c0056434.html

From: Troels Arvin on 6 Mar 2010 15:32
Hello,

blazer462 wrote:
> This updates the last used status for tables and indexes.

Thanks; that makes sense. But it makes less sense that the db2lused
session seems to be running in Executing mode long after the user has
stopped performing activity in the database.

--
Troels
 | 
Pages: 1
Prev: Making DB2 be I/O aggressive
Next: Whitepaper on Location Intelligence