Return
-
Title
unable to set or reset param SP_QUE_Q_SHMSIZE, SP_QUE_POST_SHMSIZE, SP_QUE_SHMDBUF, and SP_SHS_SHMSIZE -
Description
After the parameters SP_QUE_POST_SHMSIZE, SP_QUE_Q_SHMSIZE are changed event log records the parameter change, but list param modified does not show the change.
-
Cause
Some parameters require the sp_cop process to be stopped and restarted to take effect. -
Resolution
The parameters SP_QUE_Q_SHMSIZE, SP_QUE_POST_SHMSIZE, SP_QUE_SHMDBUF, and SP_SHS_SHMSIZE all require the sp_cop process to be bounced after setting the parameter for the changes to take effect.Changing these parameters in sp_ctrl with the set param command does not show up in a list param modified output.It shows only after bouncing sp_ copExample:Set the parameter in sp_ctrlsp_ctrl (dylan:8606)> set param SP_QUE_Q_SHMSIZE 16The parameter change does not show up in the list param modified output.sp_ctrl (dylan:8606)> list param modifiedControl Process parameters:Parameter Name Actual Value Units Set At------------------------------ ------------------------------------ ------- ---------------SP_COP_TPORT 8606 Restart CopDefault Value: 2100SP_COP_UPORT 8606 Restart CopDefault Value: 2100It does show up in the vardir/data/paramdb file with the old and new parameter values.SP_QUE_Q_SHMSIZE 8 16 # Queue shared-memory SizeAfter sp_cop shutdown paramdb is the sameSP_QUE_Q_SHMSIZE 8 16 # Queue shared-memory SizeAfter sp_cop startup paramdb file is changedSP_QUE_Q_SHMSIZE "16" # Queue shared-memory Sizeand list param modified shows below after the cop has been shutdown and restarted.SharePlex Queues parameters:Parameter Name Actual Value Units Set At------------------------------ ------------------------------------ ------- ---------------SP_QUE_Q_SHMSIZE 16 Mbytes Restart CopDefault Value: 8