I’ve encountered this issue lately with a DB2 Net Search Extender (a legacy search engine Add-on for DB2 that enables free text search) implementation which has been running smooth for over a year in production until this error showed up .
Quite simply, its an out of memory condition that may happen when your program invokes a Stored Procedure that has unusual memory requirements for its input parameters or its output.
The resolution is simply to avail more heap memory to DB2 Agent Processes. This is done by increasing a DB2 configuration parameter called the Application Support Layer Heap (aslheapsz).
Execute the following steps to resolve the issue:
1. Open a DB2 “Command Window”
2. Execute the following command. The number here is completely up to your application’s needs. Each unit is 4KB, so using 500 as a value would avail 2000 KB of Heap Memory for Agent Processes.
db2 update dbm cfg using aslheapsz 500
3. Restart DB2 for the change to take effect, and you’re done.
