DB2 memory usage help

[bomahony]

Im runnign various versions of DB2 on various UNIX platforms
(Solaris / AIX).

DB2 is generally eating up about 30% of memory on these systems (4Gb
of RAM, which equates to over a gig). i want to limit DB2s memory
usage to a couple of hundred meg in total for the entire application,
but cannot seem to find out how to do this.

When i check the instance memory usage with db2mtrk, it says its only
using a few Megs. I cannot find out how to limit the whole operation
to something like 250M or 500M or there abouts.

Can anyone help?

[Dave Hughes]

bomahony wrote:

On May 29, 12:31 pm, "Dave Hughes" <d...@waveform. plus.comwrote:

bomahony wrote:

BTW is there a network GUI monitoring / administration tool
available for DB2, like Oracles Enterprise Manager?

That's the control center (db2cc) - although whether you'll find it
much use is another matter; I'm not a fan of it, personally I find
the command line the best way to administer the server - along with
the db2mc (http://db2mc.dfw.ibm.com/) tool to aid with monitoring
(only useful with DB2 9 and above, unfortunately). Anyway...

Thanks Dave

Ive used the db2cc, and also prefer the command line. I was hoping
there was some centralised tool i could use to manage lots of
instances / servers from one location.... Guess not ...

Well, yeah, that's the db2cc - you can manage multiple instances /
servers from db2cc running on a client, provided the client has all the
instances one wishes to manage cataloged correctly (i.e. both the
remote database and administration instances must be cataloged with all
necessary details).

For example, let's say we've got a couple of DB2 servers called F and G
which each have a bog standard db2inst1 database instance, containing
SAMPLE and TOOLSDB databases, and an administration instance. The
following commands could be used to "fully" catalog the instances and
databases such that they could be remotely administered with db2cc
(specifically, things like SYSTEM must be included to tie database and
administration instances together, and I think REMOTE_INSTANCE needs
specifying too - things that might usually be ommitted from cataloging
commands):

-- Catalog the database instances
CATALOG TCPIP NODE F
REMOTE f.localdomain SERVER 60000
REMOTE_INSTANCE db2inst1
SYSTEM F
OSTYPE LINUX;
CATALOG TCPIP NODE G
REMOTE g.localdomain SERVER 60000
REMOTE_INSTANCE db2inst1
SYSTEM G
OSTYPE LINUX;

-- Catalog the admin instances
CATALOG ADMIN TCPIP NODE FDAS
REMOTE f.localdomain
SYSTEM F;
CATALOG ADMIN TCPIP NODE GDAS
REMOTE g.localdomain
SYSTEM G;

-- Catalog the databases
CATALOG DB TOOLSDB AS FTOOLS AT NODE F;
CATALOG DB SAMPLE AS FSAMPLE AT NODE F;
CATALOG DB TOOLSDB AS GTOOLS AT NODE G;
CATALOG DB SAMPLE AS GSAMPLE AT NODE G;
Still, I'd stick to the command line - better for automating changes to
several servers via scripting and such like :-)

Do check out db2mc for your v9 server though. It doesn't need to run on
the server itself, just on any old box with a DB2 client + Apache + PHP
(and the ibm_db2 php driver). Provided the databases to monitor are
cataloged on the client it should work fine and provides handy screens
like memory usage, buffer pool hit ratios, the dynamic SQL cache, etc.
etc.

(incidentally, db2mc doesn't care about things like administration
instances being cataloged - it uses the new administrative stored
procedures and table functions introduced in DB2 9 to do its stuff)
Cheers,

Dave.

[bomahony]

<snip>

(incidentally, db2mc doesn't care about things like administration
instances being cataloged - it uses the new administrative stored
procedures and table functions introduced in DB2 9 to do its stuff)

Cheers,

Dave

Dave is this in DB2 v9 or v9.5? someone else stated it was just
9.5.....

[Dave Hughes]

bomahony wrote:

<snip>

(incidentally, db2mc doesn't care about things like administration
instances being cataloged - it uses the new administrative stored
procedures and table functions introduced in DB2 9 to do its stuff)

Cheers,

Dave

Dave is this in DB2 v9 or v9.5? someone else stated it was just
9.5.....

I'm a bit fuzzy on this (I didn't get much chance to play with 9 - our
production jumped straight from 8 to 9.5), but as I understand it:

DB2 9 introduced a load of administrative stored procedures, some
views, and extended some existing ones from 8 like ADMIN_CMD to work
with lots more things.

DB2 9.5 added a whole pile of administrative views ontop of the
snapshot procedures, and added a few more stored procs itself (you'd
have to check the release notes or compare the infocenters to find out
which ones - I don't know offhand).

I've played with db2mc on 8, 9 (briefly), and 9.5. On 8, almost nothing
works (hardly surprising as it's not really meant to run with it :-).
On 9 I vaguely recall that many of the reports seemed to function
although there was the odd page that complained about a missing
view/proc, and I suspect some of the "actions" one could carry out like
forcing connections might not work. Naturally, everything works on 9.5.
Cheers,

Dave.