-
Title
Export fails to connect to the Import process with errors in target event_log -
Description
Export on the source server fails to connect to the Import process on the target.
Error from Source event_log:
Info 2013-03-06 15:45:57.182000 14272 14228 Export connected to import on XXXXXX
Error 2013-03-06 15:45:57.291000 14272 14228 Export: sp_xport: couldn't write data to socket - too many EINTR retries (exporting to XXXXXX queue XXXXXX) [module xpt]
Error 2013-03-06 15:45:57.291000 14272 14228 Export: sp_xport: failed to send message to import - exiting (exporting to XXXXXX queue XXXXXX) [module xpt]
Info 2013-03-06 15:46:07.415000 7784 17932 Export exited with code=1, pid = 15172 (exporting to XXXXXX queue XXXXXX)
Info 2013-03-06 15:50:56.503000 15588 20280 Export launched, pid = 15588 (exporting to XXXXXX queue XXXXXX)Errors from Target event_log:
Notice 2013-03-06 14:35:39.404000 16796 2784 Import: Maximum number of queues already exist (importing from XXXXXX queue XXXXXX) [module que]
Notice 2013-03-06 14:35:39.404000 16796 2784 Import: Shutdown SharePlex and increase the SP_QUE_MAX_QUEUES parameter (importing from XXXXXX queue XXXXXX) [module que]
Error 2013-03-06 14:35:39.404000 16796 2784 Import: Error add user queue rv=16 que_adduser(filehandle+P+o.olt1-o.oltp14,+PI+XXXXXX+sp_mport+0x0a37501b) (importing from XXXXXX queue XXXXXX) [module rim]
Info 2013-03-06 14:35:42.414000 12940 10844 Import exited with code=1, pid = 8236 (importing from XXXXXX queue XXXXXX)
Info 2013-03-06 14:40:39.941000 1808 13932 Import launched, pid = 1808 (importing from XXXXXX queue XXXXXX) -
Cause
Error on the event_log is generic and can occur with many reasons. It could be with the network disconnect or even with the queue corruption on the target. In such cases, target event_log provides more information. -
Resolution
To check for the network issues, refer to the steps from Knowledge Base article 12333 and run socket test utility on both source and target.
If there are messages related to queue corruption in the target event_log, contact SharePlex Technical support for help in fixing the queue corruption.
If the error is related to the number of queues in replication, Shutdown SharePlex on Source and Target, increase the SP_QUE_MAX_QUEUES parameter to a higher number. Maximum number of queues per cop is 1024, it is controlled by SP_QUE_MAX_QUEUES parameter and default is 25.
-
Additional Information
Refer to the Admin guide for additional information on setting SP_QUE_MAX_QUEUES for named queues.