Exceeded RDS Limit

Jim Keister

Exceeded RDS Limit
We use the Boole (BMC) DB2 Monitor and are receiving many 'exceeded RDS limit' errors from our online application. Our current RID Pool is allocated at 250 blks. Will increasing the RID Pool blks help to resolve the 'exceeded RDS limit' errors?
--
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

Meet Singles
http://corp.mail.com/lavalife



Wayne Driscoll

Re: Exceeded RDS Limit
(in response to Jim Keister)
Jim,
I realize that this will stun you, but "it depends." The RDS limit can be
exceeded for one of two reasons. The first reason is that the number of RID
entries was larger than 25% of the table size. The second reason is that
the number of RID entries that can fit into the guarenteed number of RID
blocks was exceeded. The second will only occur when the RID Blocks
Allocated Maximum approaches the RID list storage size.
If your'e not seeing a high value for RID blocks allocated Maximum, then
increasing the size of the RID pool won't help.
Wayne Driscoll
Product Developer
Quest Software Inc.
[login to unmask email]
Note: All opinions are strictly my own.

-----Original Message-----
From: jim keister [mailto:[login to unmask email]
Sent: Thursday, December 19, 2002 5:03 PM
To: [login to unmask email]
Subject: [DB2-L] Exceeded RDS Limit


We use the Boole (BMC) DB2 Monitor and are receiving many 'exceeded RDS
limit' errors from our online application. Our current RID Pool is
allocated at 250 blks. Will increasing the RID Pool blks help to resolve
the 'exceeded RDS limit' errors?
--

Vijay Subramanyam

Re: Exceeded RDS Limit
(in response to Wayne Driscoll)
Jim,

One of the possibility is that packages bound with old runstats could cause
this problem as DB2 thinks that 25% of table rows limit has reached (based
on old stats and when package was bound) while in reality it could be much
less than 25%. So a Runstats followed by a rebind may solve this problem.

Regards,
VIJAY

-----Original Message-----
From: jim keister
To: [login to unmask email]
Sent: 12/20/02 4:02 AM
Subject: Exceeded RDS Limit

We use the Boole (BMC) DB2 Monitor and are receiving many 'exceeded RDS
limit' errors from our online application. Our current RID Pool is
allocated at 250 blks. Will increasing the RID Pool blks help to
resolve the 'exceeded RDS limit' errors?
--
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

Meet Singles
http://corp.mail.com/lavalife



the DB2-L webpage at http://listserv.ylassoc.com. The owners of the list
can
WARNING: The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this message
by anyone else is unauthorised. If you are not the intended recipient, any
disclosure, copying, or distribution of the message, or any action or
omission taken by you in reliance on it, is prohibited and may be unlawful.
Please immediately contact the sender if you have received this message in
error. Thank you.



Vijay Subramanyam

Re: Exceeded RDS Limit
(in response to Vijay Subramanyam)
Jim,

One of the possibility is that packages bound with old runstats could cause
this problem as DB2 thinks that 25% of table rows limit has reached based on
old stats and when package was bound, while in reality it could be much less
than 25%. So a Runstats followed by a rebind may solve this problem.

Regards,
VIJAY


-----Original Message-----
From: jim keister
To: [login to unmask email]
Sent: 12/20/02 4:02 AM
Subject: Exceeded RDS Limit

We use the Boole (BMC) DB2 Monitor and are receiving many 'exceeded RDS
limit' errors from our online application. Our current RID Pool is
allocated at 250 blks. Will increasing the RID Pool blks help to
resolve the 'exceeded RDS limit' errors?
--
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

Meet Singles
http://corp.mail.com/lavalife



the DB2-L webpage at http://listserv.ylassoc.com. The owners of the list
can
WARNING: The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this message
by anyone else is unauthorised. If you are not the intended recipient, any
disclosure, copying, or distribution of the message, or any action or
omission taken by you in reliance on it, is prohibited and may be unlawful.
Please immediately contact the sender if you have received this message in
error. Thank you.