Export and Import fail to connect with messages “Export: Send_queuedata failed to send message to import – exiting” on source and “Import: Failure writing to queues – exiting” on target (4300999)

Export and Import fail to connect with messages “Export: Send_queuedata failed to send message to import – exiting” on source and “Import: Failure writing to queues – exiting” on target

The following messages are observed in source and target event_log when Export fails to send messages to target and consequently the Export queue keeps growing:

Source:

Error    2017-04-20 19:58:43.998180 14041 1 Export: Send_queuedata failed to send message to import - exiting  (exporting to server_name queue queue_name) [module xpt]

Error    2017-04-20 19:58:43.994165 14041 1 Export: Failed to send message mid 8259 to sp_mport  (exporting to server_name queue queue_name) [module xpt]

Error    2017-04-20 19:58:43.992341 14041 1 Export: Couldn't write data to socket  (exporting to server_name queue queue_name) [module xpt]

Error    2017-04-20 19:58:43.989404 14041 1 Export: Broken pipe - write error  (exporting to server_name queue queue_name) [module xpt]

corresponding messages in Target event log:

Info     2017-04-20 16:38:44.894073 17817 1 Import exited with code=1, pid = 4311  (importing from server_name queue queue_name)

Error    2017-04-20 16:38:44.888666 4311 1 Import: Failure writing to queues - exiting  (importing from server_name queue queue_name) [module imp]

Notice   2017-04-20 16:38:44.887659 4311 1 Import: Error opening output queue que_ERR: Non specific error que_open(-,queue_name+P+o.SID1-o.SID2,0xnnnnnn+PI+queue_name+sp_mport+0xnnnnnn)  (importing from server_name queue queue_name) [module rim]

Error    2017-04-20 16:38:44.886245 4311 1 Import: No such file or directory que_open.open_fd  (importing from server_name queue queue_name) [module que]

Info     2017-04-20 16:38:44.884665 4311 1 Import connected to export on server_name

Info     2017-04-20 16:38:44.544963 4311 1 Import launched, pid = 4311  (importing from server_name queue queue_name)

There is a Post queue corruption on target.

Unless the queue corruption is resolved, the replication cannot resume. Unfortunately, the extent of data loss in the event of queue corruption cannot be pre-ascertained so fixing the queue corruption is the only way out. Since there is a likelihood of data loss, one may want to monitor the target sp_ctrl and periodically issue “show sync” to look for any impending out of sync. A more proactive approach would be to resync the target at a later time. Feel free to contact Support in case of any questions or if the above does not help.