Optimized Query / Created Index (Memory Error) 1

[onpnt]

I optimized a query that was seriously killing the prformance of a load job and in this optimization created an index on one of our tables. Not sure if the details beyond that are needed but if they ar please ask.

Anyhow, after doing this we're getting an error back from the DB2 instance as

This query is hit several thousand times to generat the required output and I think this situation was just not sen until the query was optimized and we went from hours to minutes so I'm obviously thinking memory is not bing rleasd somwhere and would like to know if this is an easy change if someone has seen this error? I'm newr to DB2 obviously from my pervious jump into this forums contribution but am still sorting resarching this and would like suggestions if someone knows anything Thanks all

_{____________ signature below ______________
You are a amateur developer until you realize all your code sucks.
Jeff Atwood}

 

[blom0344]

From IBM's resources:

Get instance sort threshold and database heap size for sort:
# db2 get dbm cfg | grep SHEAPTHRES
# db2 get db cfg for rmdb | grep SORTHEAP

Update sort size to 2MB:
# db2 update db cfg for RMDB using SORTHEAP 512

make sure that you do not set sortheap higher than sheapthres.

Ties Blom

 

[onpnt]

Thanks Ties. Late last night I found the same doc and altered the heap threshhold a few times and it did fix the problem.



_{____________ signature below ______________
You are a amateur developer until you realize all your code sucks.
Jeff Atwood}