SYMPTOM:
When the number of threads and their priorities are altered using Strategy Command Manager, the changes are not immediately reflected.
Consider the following example where an Administrator changes the priority threads in Strategy Desktop to zero so that no jobs can be executed to the warehouse:
After a certain time period, the Administrator decides to change the priority threads back to their original state by executing the following Command Manager script:
ALTER DBINSTANCE "Development Warehouse" HIGHTHREADS 20 MEDIUMTHREADS 2 LOWTHREADS 2;
After script execution, jobs that are submitted are listed in a 'waiting' state because the Command Manager script was not applied.
CAUSE:
This issue is caused because the Strategy Command Manager script did not specify to apply on 'run time settings.' This issue does not occur if changes in thread priorities are made via the Strategy Desktop interface. In Strategy Desktop, changes are automatically applied to run time objects in the Strategy Intelligence Server.
ACTION:
To resolve this issue, add the following line at the end of the Strategy Command Manager script: "APPLY RUN TIME SETTINGS"
ALTER DBINSTANCE " Development Warehouse " HIGHTHREADS 20 MEDIUMTHREADS 2 LOWTHREADS 2;
APPLY RUN TIME SETTINGS;
