-
Title
The compare client errored out with "Error: shs_get_stat for queue_reader" and now sp_cop does no -
Description
The compare client errored out and the sp_cop is not able to start. The following are the event log indicating some issues with compare processes on target:
05/18/10 11:14 Child process failed: sp_declt stopped due to SIGTERM
05/18/10 11:14 Warning: sp_declt didn't shutdown [sp_cop/20012]
05/18/10 11:14 Process exited sp_declt (for o.SID1-o.SID2-2767142464) [pid = 1067] - killed due to SIGTERM
.
05/18/10 17:03 Error: shs_get_stat for POST_QUEUE_NAME+P+o.SID1-o.SID2+U+POST_QUEUE_NAME+sp_declt+o.SID1-o.SID2-2798607968 : shs_NOTFOUND: requested statistic does not exist [qview(que)/22212]
05/18/10 17:05 Error: shs_get_stat for POST_QUEUE_NAME+P+o.SID1-o.SID2+U+POST_QUEUE_NAME+sp_declt+o.SID1-o.SID2-2759220657 : shs_NOTFOUND: requested statistic does not exist [qview(que)/23884]
05/18/10 17:05 Notice: Result (22) Invalid argument calling shmat to attach to shared memory segment (1002) [qview(shs)/24209]
05/18/10 17:05 Error: shs_init_shm.shmat [qview(shs)/24209]
The qview could be launched but qsetup could not be launched even after killing Shareplex orphaned processes. There are no compare client processes observed at the OS level when issuing ps -ef | grep sp_declt -
Cause
It may be the case of orphaned Compare client Readers in the Post queue.
 -
Resolution
First remove any hung semaphores which may typically be present in such situations (see Solution # SOL6531 for details). Then carry out the following steps.
A quick way to try resolving the issue without causing any damage to the queue is to run fixusers command as below. If it gives the output as below, then the command is successful in removing the orphaned Readers:
$ qview -i
qview> fixusers POST_QUEUE_NAME+P+o.SID1-o.SID2
Remove 2:+U+POST_QUEUE_NAME+sp_declt+o.SID1-o.SID2-2798607968
Remove 3:+U+POST_QUEUE_NAME+sp_declt+o.SID1-o.SID2-2759220657Shareplex should be able to start after this. If in doubt about running the fixusers command, or if the above does not help, then contact Support.
Â