DB2 8.2 FP5 (8.1 FP12) on SLES 9 SP3.

The portal 6 infocenter instructs you to run the following commands to confi
gure the DB2 server.
db2set DB2_RR_TO_RS=yes
db2set DB2_EVALUNCOMMITTED=YES
db2set DB2_INLIST_TO_NLJN=YES
db2 "UPDATE DBM CFG USING query_heap_sz 32768"
db2 "UPDATE DBM CFG USING maxagents 500"
db2 "UPDATE DBM CFG USING sortheap_thres 50000"

The last command fails with the following message:
SQL0104N  An unexpected token "sortheap_thres" was found following "USING".
Expected tokens may include:  "AGENTPRI".  SQLSTATE=42601

[ Post a follow-up to this message ]

The infocenter for WebSphere Portal 6 is incorrect.  I found the resolution.

The DB2 config parameter sortheap_thres does not exist (see the following co
mmands).  It is actually called SHEAPTHRES.

So the infocenter instructs you to run this command:
db2 "UPDATE DBM CFG USING sortheap_thres 50000"

But you should really run this command:
db2 "UPDATE DBM CFG USING SHEAPTHRES 50000"



db2inst1@portal6db:~> DB2 get dbm cfg | grep -i sort
Sort                                   (DFT_MON_SORT) = OFF
Sort heap threshold (4KB)                  (SHEAPTHRES) = 20000
db2inst1@portal6db:~> DB2 "UPDATE DBM CFG USING SHEAPTHRES 50000"
DB20000I  The UPDATE DATABASE MANAGER CONFIGURATION command completed
successfully.
db2inst1@portal6db:~> DB2 get dbm cfg | grep -i sort
Sort                                   (DFT_MON_SORT) = OFF
Sort heap threshold (4KB)                  (SHEAPTHRES) = 50000
db2inst1@portal6db:~>

[ Post a follow-up to this message ]