All -

DB2 LUW 9.1.4 under AIX 6...How to tell how many and which are active
DB's I have under an instance...given this:

Max number of concurrently active databases (NUMDB) = 8

If I do:

'db2 list applications' and count-up the nbr of connections by DB...
Assuming I have 10 databases on an instance and find: DB X has 4
connections, DB Y has 5 connections, DB Z has 3 connections then I
have 3 active DB's and 6 inactive DB's, right? and I can therefore
know which 3 of the 10 are active. Does this rule ALWAYS hold true?

IE if it doesn't show any active connections in List Applications then
it should be obvious which DB's are active and which are not...I know
it seems like a rookie 101 question but I'm just trying to ensure that
it always holds true...

On Apr 28, 9:28*am, Bruce <bwmille... (AT) gmail (DOT) com> wrote:
I wish I could add...yikes its scary...but 10 db's in total...3 active
leaves 7 inactive !!!

On 2011-04-28 15:28, Bruce wrote:

A database can be activated but not have any connections.
An activated database has memory allocated.
You could use db2pd to find out the details.
Your assumption above holds true if databases never are activated explicitly.

/dg

On Apr 28, 11:30*am, danfan46 <danfa... (AT) hotmail (DOT) com> wrote:
Thanks for the info...no, we normally do not ACTIVATE DB
explicitly...we just let users connect...

On Apr 28, 6:28*am, Bruce <bwmille... (AT) gmail (DOT) com> wrote:

You can use the command, 'LIST ACTIVE DATABASES'

Using LIST APPLICATIONS will only show you databases that have
connections to them; not necessarily databases that have been
activated (but don't have any connections).

You mentioned in another post you use STMM, I noticed this will let
the active databases grow until they consume all available memory.
This can cause the activation of another database to fail or to start
up only with those tiny default bufferpools (don't remember their
name) which you probably won't even notice. My advice is to keep them
activated, even if not used.

--
Frederik Engelen