Error “Compare server: shs_alloc_stat_for (2): Failed with error shs_ALLALLOCED:” (4299353)

Error “Compare server: shs_alloc_stat_for (2): Failed with error shs_ALLALLOCED:”

A very high value set for threads provided from Compare command causing shared memory issues.

Reduce the value for “threads” options in Compare command and re-run it.

For example:

sp_ctrl (alvsupu15:5438)> compare OWNER.TABLE_NAME threads 10

The value of "threads" provided in the above compare is extremely high. It should be more realistic, say something less than 15, preferably under 10. Starting with SharePlex 8.5, the "threads" option can be provided in compare command in lieu of the parameter SP_DEQ_THREADS. A high value is useful if there are more than one processor. A high value may result in diminishing returns due to the overheads that come with thread management. So the suggestion is made to use a value of 10. To set the optimum value is a matter of trial and error. Here is the description of the parameter SP_DEQ_THREADS which is a proxy for the “threads” option in compare. SP_DEQ_THREADS This parameter controls the number of processing threads used by the compare commands on the source system. Each thread creates a sp_declt process on the target machine. The default of 2 threads has proven to be the best number for UP machines, but you might obtain performance improvements with up to 15 threads. Too many threads causes diminishing benefits, especially if it causes large tables to be compared at the same time. The value for the thread count is independent of the number of tables to be compared, and SharePlex will not generate more threads than there are tables to be compared. If the machine has only one processor, set this parameter to a value of 1. Do not set it to more than the number of processors on the system. Default: 2 threads Range of valid values: 1 to 15 Takes effect: immediately available for the next comparison