The following messages are seen in event_log when Capture stopped due to error:
sp_ctrl > show log reverse
Info 2017-04-11 14:47:42.383859 4021 692008800 Capture exited with code=1, pid = 1356 (capturing from source_SID)
Error 2017-04-11 14:47:41.356357 1356 3894945632 Capture stopped: Internal error encountered; cannot continue (capturing from source_SID)
Error 2017-04-11 14:47:41.355797 1356 3894945632 Capture: 10722 - can't open capture queue que_ERR: Non specific error (capturing from source_SID) [module oct]
Error 2017-04-11 14:47:41.355319 1356 3894945632 Capture: No such file or directory que_open.open_fd (capturing from source_SID) [module que]
To fix the queue corruption, carry out the following steps:
1. Shutdown SharePlex
2. While in the /proddir/bin directory issue the following command (where proddir denotes Product Directory of SharePlex and $ denotes the OS prompt)
$ qview –i
qview>fixup all
3. Restart SharePlex
The above steps are not complicated and are not prone to error. If they do not resolve the Capture issues, then Support need to be contacted for further action. It may be noted that fixing queue corruption may involve data loss, the extent of which cannot be pre-determined. And there is no way to move forward without fixing it.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center