473,320 Members | 2,122 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,320 software developers and data experts.

DB2NTMEMSIZE

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
1 1964

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 thread has been closed and replies have been disabled. Please start a new discussion.

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.