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

DB2NTMEMSIZE

P: n/a
When ever I start DB2, I get the message that APLD has been truncated
and that I should add the param to the DB2 registry DB2NTMEMSIZE =
APLD:125830720

The documentation says that APLD is related to Fenced Stored
Procedures, can someone please advise why it would want 125mb of memory
simply for fenced stored procedures ? Does the number of SPs defined
make a difference ?

Many thanks, Tim

Apr 4 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a

p175 wrote:
When ever I start DB2, I get the message that APLD has been truncated
and that I should add the param to the DB2 registry DB2NTMEMSIZE =
APLD:125830720

The documentation says that APLD is related to Fenced Stored
Procedures, can someone please advise why it would want 125mb of memory
simply for fenced stored procedures ? Does the number of SPs defined
make a difference ?

Many thanks, Tim


Hi Tim,

The DB2 engine needs to be able to send data to/from each running
stored procedure. So, this memory is related to the number of active
SPs at a time, not the number that are defined. If you know that you
only have a small number of fenced SPs running at a time, you won't
need a large APLD set, so you can ignore this warning.

You can use the ASLHEAPSZ DBM configuration parameter to control the
size of the APLD set, as well as the DB2_FMP_COMM_HEAPSZ registry
variable (look in your docs for descriptions of these 2 parameters).

Cheers,
Liam.

Apr 4 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.