Unix Technical Forum

DB2DIAG.log Error

This is a discussion on DB2DIAG.log Error within the DB2 forums, part of the Database Server Software category; --> 2006-08-14-17.46.13.656000-240 I1472H436 LEVEL: Warning PID : 1452 TID : 336 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB ...


Go Back   Unix Technical Forum > Database Server Software > DB2

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 02-27-2008, 07:54 AM
p175
 
Posts: n/a
Default DB2DIAG.log Error

2006-08-14-17.46.13.656000-240 I1472H436 LEVEL: Warning
PID : 1452 TID : 336 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SQ4V6
APPHDL : 0-9 APPID: *LOCAL.DB2.060814214011
AUTHID : DB2ADMIN
FUNCTION: DB2 UDB, Self tuning memory manager,
stmmEnforceMinSizeConstraints, probe:2089
MESSAGE : Unable to find donor to satisfy minSize constraint

Does anyone have any idea what this means and how I can resolve it ?

DB2 Express C v9 on win2k.

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 02-27-2008, 07:54 AM
tommy
 
Posts: n/a
Default Re: DB2DIAG.log Error

u can check db's buffer pool and other share memory's size
maybe ,when u restore the db from other server,and that server's memory
size bigger than this one.

p175 wrote:
> 2006-08-14-17.46.13.656000-240 I1472H436 LEVEL: Warning
> PID : 1452 TID : 336 PROC : db2syscs.exe
> INSTANCE: DB2 NODE : 000 DB : SQ4V6
> APPHDL : 0-9 APPID: *LOCAL.DB2.060814214011
> AUTHID : DB2ADMIN
> FUNCTION: DB2 UDB, Self tuning memory manager,
> stmmEnforceMinSizeConstraints, probe:2089
> MESSAGE : Unable to find donor to satisfy minSize constraint
>
> Does anyone have any idea what this means and how I can resolve it ?
>
> DB2 Express C v9 on win2k.


Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 02-27-2008, 07:54 AM
Serge Rielau
 
Posts: n/a
Default Re: DB2DIAG.log Error

p175 wrote:
> 2006-08-14-17.46.13.656000-240 I1472H436 LEVEL: Warning
> PID : 1452 TID : 336 PROC : db2syscs.exe
> INSTANCE: DB2 NODE : 000 DB : SQ4V6
> APPHDL : 0-9 APPID: *LOCAL.DB2.060814214011
> AUTHID : DB2ADMIN
> FUNCTION: DB2 UDB, Self tuning memory manager,
> stmmEnforceMinSizeConstraints, probe:2089
> MESSAGE : Unable to find donor to satisfy minSize constraint
>
> Does anyone have any idea what this means and how I can resolve it ?

Your minimum memory configuration cannot be satisfied because there
aren't enough resources.
The most likely culprit for outrageous memory requests in a 32bit system
would be the number of agents which multiplies with the agent private
memory pools.
If you dump you your DB and DBM CFG settings chances are something is
out of wack.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

IOD Conference
http://www.ibm.com/software/data/ond...ness/conf2006/
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 02-27-2008, 07:55 AM
p175
 
Posts: n/a
Default Re: DB2DIAG.log Error

Serge, a question if I might.

If I have only two [2] users so to speak, then what would be the
recommended number of agents given I am running on win2k 2000 with
Express C 9.1 subject to windows 1.7gb 32bit memory restrictions ? I
have 2.5gb installed.

I am the only user running stored procedures and these always happen
consequtively, not concurently, always committed inbetween. I have one
other bloke that does the occasional query throughout the day. Stored
procedures are only run once a day within a two hour window and no
queries are executed during this timeframe, is there a need to support
a great number of agents, or could I reduce the available pool to allow
more memory to the BPs etc ?

db2 get dbm cfg

Database Manager Configuration

Node type = Database Server with local and remote clients

Database manager configuration release level = 0x0b00


Max number of concurrently active databases (NUMDB) = 3
Federated Database System Support (FEDERATED) = NO
Transaction processor monitor name (TP_MON_NAME) =

Database monitor heap size (4KB) (MON_HEAP_SZ) = 512
Java Virtual Machine heap size (4KB) (JAVA_HEAP_SZ) = 512
Audit buffer size (4KB) (AUDIT_BUF_SZ) = 0
Size of instance shared memory (4KB) (INSTANCE_MEMORY) = AUTOMATIC
Backup buffer default size (4KB) (BACKBUFSZ) = 4096
Restore buffer default size (4KB) (RESTBUFSZ) = 4096
Agent stack size (AGENT_STACK_SZ) = 32
Minimum committed private memory (4KB) (MIN_PRIV_MEM) = 32
Private memory threshold (4KB) (PRIV_MEM_THRESH) = 20000
Sort heap threshold (4KB) (SHEAPTHRES) = 0
Directory cache support (DIR_CACHE) = YES
Application support layer heap size (4KB) (ASLHEAPSZ) = 512
Max requester I/O block size (bytes) (RQRIOBLK) = 32767
DOS requester I/O block size (bytes) (DOS_RQRIOBLK) = 4096
Query heap size (4KB) (QUERY_HEAP_SZ) = 2048

Priority of agents (AGENTPRI) = SYSTEM
Max number of existing agents (MAXAGENTS) = 200
Agent pool size (NUM_POOLAGENTS) =
100(calculated)
Initial number of agents in pool (NUM_INITAGENTS) = 0
Max number of coordinating agents (MAX_COORDAGENTS) = (MAXAGENTS -
NUM_INIT
AGENTS)
Max no. of concurrent coordinating agents (MAXCAGENTS) =
MAX_COORDAGENTS
Max number of client connections (MAX_CONNECTIONS) =
MAX_COORDAGENTS

Keep fenced process (KEEPFENCED) = YES
Number of pooled fenced processes (FENCED_POOL) =
MAX_COORDAGENTS
Initial number of fenced processes (NUM_INITFENCED) = 0

Maximum query degree of parallelism (MAX_QUERYDEGREE) = ANY
Enable intra-partition parallelism (INTRA_PARALLEL) = YES

No. of int. communication buffers(4KB)(FCM_NUM_BUFFERS) = AUTOMATIC
No. of int. communication channels (FCM_NUM_CHANNELS) = AUTOMATIC


db2 get db cfg for DB1

Database Configuration for Database DB1

Database configuration release level = 0x0b00
Database release level = 0x0b00

Database territory = US
Database code page = 1252
Database code set = IBM-1252
Database country/region code = 1
Database collating sequence = UNIQUE
Alternate collating sequence (ALT_COLLATE) =
Database page size = 4096
Dynamic SQL Query management (DYN_QUERY_MGMT) = DISABLE
Discovery support for this database (DISCOVER_DB) = ENABLE
Restrict access = NO
Default query optimization class (DFT_QUERYOPT) = 5
Degree of parallelism (DFT_DEGREE) = ANY
Continue upon arithmetic exceptions (DFT_SQLMATHWARN) = NO
Default refresh age (DFT_REFRESH_AGE) =
99999999999999
Default maintained table types for opt (DFT_MTTB_TYPES) = SYSTEM
Number of frequent values retained (NUM_FREQVALUES) = 50
Number of quantiles retained (NUM_QUANTILES) = 50
Backup pending = NO
Database is consistent = NO
Rollforward pending = NO
Restore pending = NO
Multi-page file allocation enabled = YES
Log retain for recovery status = NO
User exit for logging status = NO
Self tuning memory (SELF_TUNING_MEM) = ON
Size of database shared memory (4KB) (DATABASE_MEMORY) = AUTOMATIC
Database memory threshold (DB_MEM_THRESH) = 10
Max storage for lock list (4KB) (LOCKLIST) = AUTOMATIC
Percent. of lock lists per application (MAXLOCKS) = AUTOMATIC
Package cache size (4KB) (PCKCACHESZ) = AUTOMATIC
Sort heap thres for shared sorts (4KB) (SHEAPTHRES_SHR) = AUTOMATIC
Sort list heap (4KB) (SORTHEAP) = AUTOMATIC
Database heap (4KB) (DBHEAP) = 20240
Catalog cache size (4KB) (CATALOGCACHE_SZ) = 570
Log buffer size (4KB) (LOGBUFSZ) = 4096
Utilities heap size (4KB) (UTIL_HEAP_SZ) = 59513
Buffer pool size (pages) (BUFFPAGE) = 10000
Max size of appl. group mem set (4KB) (APPGROUP_MEM_SZ) = 11789
Percent of mem for appl. group heap (GROUPHEAP_RATIO) = 70
Max appl. control heap size (4KB) (APP_CTL_HEAP_SZ) = 128
SQL statement heap (4KB) (STMTHEAP) = 8192
Default application heap (4KB) (APPLHEAPSZ) = 256
Statistics heap size (4KB) (STAT_HEAP_SZ) = 4384
Interval for checking deadlock (ms) (DLCHKTIME) = 10000
Lock timeout (sec) (LOCKTIMEOUT) = -1
Changed pages threshold (CHNGPGS_THRESH) = 80
Number of asynchronous page cleaners (NUM_IOCLEANERS) = AUTOMATIC
Number of I/O servers (NUM_IOSERVERS) = AUTOMATIC
Index sort flag (INDEXSORT) = YES
Sequential detect flag (SEQDETECT) = YES
Default prefetch size (pages) (DFT_PREFETCH_SZ) = 48
Track modified pages (TRACKMOD) = OFF
Default number of containers = 1
Default tablespace extentsize (pages) (DFT_EXTENT_SZ) = 24
Max number of active applications (MAXAPPLS) = 40
Average number of active applications (AVG_APPLS) = 1
Max DB files open per application (MAXFILOP) = 64
Log file size (4KB) (LOGFILSIZ) = 15000
Number of primary log files (LOGPRIMARY) = 25
Number of secondary log files (LOGSECOND) = 100
Changed path to log files (NEWLOGPATH) =
Path to log files =
D:\DB2\CONTAINERS\DB1\LOGS\NODE0000\
Overflow log path (OVERFLOWLOGPATH) =
Mirror log path (MIRRORLOGPATH) =
First active log file =
Block log on disk full (BLK_LOG_DSK_FUL) = YES
Percent max primary log space by transaction (MAX_LOG) = 0
Num. of active log files for 1 active UOW(NUM_LOG_SPAN) = 0
Group commit count (MINCOMMIT) = 1
Percent log file reclaimed before soft chckpt (SOFTMAX) = 680
Log retain for recovery enabled (LOGRETAIN) = OFF
User exit for logging enabled (USEREXIT) = OFF

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #5 (permalink)  
Old 02-27-2008, 07:55 AM
Serge Rielau
 
Posts: n/a
Default Re: DB2DIAG.log Error

p175 wrote:
> Serge, a question if I might.
>
> If I have only two [2] users so to speak, then what would be the
> recommended number of agents given I am running on win2k 2000 with
> Express C 9.1 subject to windows 1.7gb 32bit memory restrictions ? I
> have 2.5gb installed.
>
> I am the only user running stored procedures and these always happen
> consequtively, not concurently, always committed inbetween. I have one
> other bloke that does the occasional query throughout the day. Stored
> procedures are only run once a day within a two hour window and no
> queries are executed during this timeframe, is there a need to support
> a great number of agents, or could I reduce the available pool to allow
> more memory to the BPs etc ?
>

I leave comments on the cfg settings to others..
You don't need many agents. In your case a handful will be plenty.
I would probably keep the minpool agents at 2.
But the way things are set up the number of agents shouldn't be your issue.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

IOD Conference
http://www.ibm.com/software/data/ond...ness/conf2006/
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #6 (permalink)  
Old 02-27-2008, 07:55 AM
Knut Stolze
 
Posts: n/a
Default Re: DB2DIAG.log Error

p175 wrote:

> Serge, a question if I might.
>
> If I have only two [2] users so to speak, then what would be the
> recommended number of agents given I am running on win2k 2000 with
> Express C 9.1 subject to windows 1.7gb 32bit memory restrictions ? I
> have 2.5gb installed.


If you have only simple statements that won't benefit from parallel
execution, then 2 agents would be sufficient - theoretically.

My proposal would be that you run the Configuration Advisor and have a look
at the suggestions given by that tool.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #7 (permalink)  
Old 02-27-2008, 07:55 AM
Serge Rielau
 
Posts: n/a
Default Re: DB2DIAG.log Error

Serge Rielau wrote:
> p175 wrote:
>> Serge, a question if I might.
>>
>> If I have only two [2] users so to speak, then what would be the
>> recommended number of agents given I am running on win2k 2000 with
>> Express C 9.1 subject to windows 1.7gb 32bit memory restrictions ? I
>> have 2.5gb installed.
>>
>> I am the only user running stored procedures and these always happen
>> consequtively, not concurently, always committed inbetween. I have one
>> other bloke that does the occasional query throughout the day. Stored
>> procedures are only run once a day within a two hour window and no
>> queries are executed during this timeframe, is there a need to support
>> a great number of agents, or could I reduce the available pool to allow
>> more memory to the BPs etc ?
>>

> I leave comments on the cfg settings to others..
> You don't need many agents. In your case a handful will be plenty.
> I would probably keep the minpool agents at 2.
> But the way things are set up the number of agents shouldn't be your issue.
>
> Cheers
> Serge

Can you send me your db2diag log and teh content of
"sqllib/db2dump/stmmlog called stmm.<N>.log, the record format is like
the ones in db2diag.log. On Windows they are in sqllib/<instance>/stmmlog"
I'll pass it along.
Note that this group is not moderated, so consider posting support-like
questions in the DB2 Express C forum. Rahul or one of the other
moderators are better equipped to handle when they need backstage help.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

IOD Conference
http://www.ibm.com/software/data/ond...ness/conf2006/
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 07:54 AM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
www.UnixAdminTalk.com