Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / January 2008

Tip: Looking for answers? Try searching our database.

Question on get db cfg

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
datapro01 - 21 Jan 2008 18:49 GMT
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.
Lennart - 21 Jan 2008 19:21 GMT
[...]

> 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 <db> show detail

      Database Configuration for Database <db>

Description                                   Parameter   Current
Value              Delayed Value

---------------------------------------------------------------------------------------------------------------
[...]

HTH
/Lennart
datapro01 - 21 Jan 2008 20:13 GMT
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.
Ian - 21 Jan 2008 21:03 GMT
> 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.
datapro01 - 22 Jan 2008 13:16 GMT
> > I understand what you are saying and am aware of that.
>
[quoted text clipped - 5 lines]
>
> 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?
Roger - 22 Jan 2008 14:18 GMT
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?
Ian - 23 Jan 2008 10:47 GMT
>>> 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
[quoted text clipped - 7 lines]
> 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.
datapro01 - 23 Jan 2008 20:09 GMT
Thanks Ian
datapro01 - 29 Jan 2008 19:28 GMT
> 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
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.