By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,505 Members | 1,206 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,505 IT Pros & Developers. It's quick & easy.

Question on get db cfg

P: n/a
When issuing a get db cfg command are we supposed to be getting the
current value or future value of a parameter?

For example, I issue a get db cfg against a certain database and get
this:

Statistics heap size (4KB) (STAT_HEAP_SZ) = 20000

If I then issue a get db cfg show detail on the same database I get
this

Statistics heap size (4KB) (STAT_HEAP_SZ) =
18000 20000

Is the get db cfg command issued by itself supposed to show a future
value?
Thanks in advance.
Jan 21 '08 #1
Share this Question
Share on Google+
8 Replies


P: n/a
On Jan 21, 7:49 pm, datapro01 <datapr...@yahoo.comwrote:
[...]
>
Statistics heap size (4KB) (STAT_HEAP_SZ) =
18000 20000

Is the get db cfg command issued by itself supposed to show a future
value?
Not all parameters can be changed immediate. Thus, what you see when
you "show detail", is a current and a pending (or delayed) value. In
your example above STAT_HEAP_SZ is 18000, but is waiting for an
opportunity to become 20000:

db2 get db cfg for <dbshow detail

Database Configuration for Database <db>

Description Parameter Current
Value Delayed Value

---------------------------------------------------------------------------------------------------------------
[...]
HTH
/Lennart
Jan 21 '08 #2

P: n/a
I understand what you are saying and am aware of that.

But why is it showing the future value (20000) in the get db cfg and
not the current value of 18000.
I ran a db2pd -db se1 -dbcfg on the db and it shows an in memory
(current) value of 18000 and a disc (future) value of 20000.

Jan 21 '08 #3

P: n/a
Ian
datapro01 wrote:
I understand what you are saying and am aware of that.

But why is it showing the future value (20000) in the get db cfg and
not the current value of 18000.
The 'GET DB CFG' command shows you what is in the database configuration
file, i.e. what is on disk.

This is why IBM added the 'SHOW DETAIL' option.

Jan 21 '08 #4

P: n/a
On Jan 21, 4:03 pm, Ian <ianb...@mobileaudio.comwrote:
datapro01 wrote:
I understand what you are saying and am aware of that.
But why is it showing the future value (20000) in the get db cfg and
not the current value of 18000.

The 'GET DB CFG' command shows you what is in the database configuration
file, i.e. what is on disk.

This is why IBM added the 'SHOW DETAIL' option.
May I ask what the meaning of what is the difference when referring
to db cfg parameters between 'in memory' and 'on disc'?
Which one is currently being used?
Jan 22 '08 #5

P: n/a
datapro01, it means you have the setting 18000 running on the
database. And when DB2 gets a chance it will increase the setting to
20000. In other words, this setting is like a windows setting that
requires a reboot to come into effect.

HTH

Roger
May I ask what the meaning of what is the difference when referring
to db cfg parameters between 'in memory' and 'on disc'?
Which one is currently being used?
Jan 22 '08 #6

P: n/a
Ian
datapro01 wrote:
On Jan 21, 4:03 pm, Ian <ianb...@mobileaudio.comwrote:
>datapro01 wrote:
>>I understand what you are saying and am aware of that.
But why is it showing the future value (20000) in the get db cfg and
not the current value of 18000.
The 'GET DB CFG' command shows you what is in the database configuration
file, i.e. what is on disk.

This is why IBM added the 'SHOW DETAIL' option.

May I ask what the meaning of what is the difference when referring
to db cfg parameters between 'in memory' and 'on disc'?
Which one is currently being used?
"In memory" means the current active value of the parameter.
"On Disk" means that value of the parameter the next time the database
is activated.

Jan 23 '08 #7

P: n/a
Thanks Ian
Jan 23 '08 #8

P: n/a
On Jan 23, 3:09 pm, datapro01 <datapr...@yahoo.comwrote:
Thanks Ian
IBM just admitted that there is a problem with the stats heap
parameter in the get db cfg command db2 version 9.

Action Taken : I tested what the customer is seeing. yes this
is
incorrect
behavior.

I updated the db cfg for STAT_HEAP_SZ from the default of 4384 to
10000
and I did not bounce db2 or deactivate the db in anyway. the results
are
below.

[phaus@ts-phaus ~]$ db2 get db cfg show detail | grep -i
STAT_HEAP_SZ
Statistics heap size (4KB) (STAT_HEAP_SZ) = 4384
10000
[phaus@ts-phaus ~]$ db2 get db cfg | grep -i
STAT_HEAP_SZ
Statistics heap size (4KB) (STAT_HEAP_SZ) =
10000

Action Plan : I will enter an APAR for
this.
..NextCT 2008-01-30
Jan 29 '08 #9

This discussion thread is closed

Replies have been disabled for this discussion.