Error received in the Target Compare's declt log:
Process launched: sp_declt (for o.SOURCE_SID-o.TARGET_SID-53420) [pid = 15360]
Notice: Opened DataEquator session log file /usr/app/TARGET_SID/splex/splex_queue/log/TARGET_SID_declt-SOURCE_SID-configuration_hlist_filter0003-26322- 01.log [sp_declt(deq)/15360]
Notice: Oracle env - TARGET_SID:/usr/app/TARGET_SID/oracle/product/10.1.0 [sp_declt(pdb)/15360] 30.01.06 15:01 Tivoli-Application-Adapter-Probe
Internal error: Can not add DataEquator queue reader, tried for 300 seconds.Error: que_TOOMANYUSERS: User table is full (processDataEquatorMsg,L771) [sp_opst (for o.SOURCE_SID-o.TARGET_SID queue queue_name)/28633]
Internal error: Can not add DataEquator queue reader, tried for 300 seconds.Error: que_TOOMANYUSERS: User table is full (processDataEquatorMsg,L771) [sp_opst (for o.SOURCE_SID-o.TARGET_SID queue queue_name)/28633]
The max number of processes that can write data to the statistics shared memory has been exceeded. The default is 2000, but can be changed with SP_SHS_SHMSIZE.
Many compare repairs are running and MTP poster is being used.
Increase SP_SHS_MAXWRITERS parameter.
SP_SHS_MAXWRITERS - This parameter sets the maximum number of Shareplex processes that can write data to the statistics shared memory. When the number of processes that allocate a statistic is equal to this limit, the error messages will appear in the Event Log, and the process will fail: Greater than maximum writers number.
In this event, the value of the SP_SHS_MAXWRITERS parameter needs to be increased. The upper limit of this parameter is determined by the size of the shared memory segment (see the SP_SHS_SHMSIZE parameter).
Internal Parameter
Default: 2000
Range of valid values: any positive integer.
Takes effect: when Shareplex is restarted.
Below is an example on how to set processes to 3000:
1. sp_ctrl> set param SP_SHS_MAXWRITERS 3000
2. Bounce sp_cop.
3. Compare.
