OGG-01232 receive TCP Params error: TCP/IP error 104 (Connection reset by peer ).

The following errors are often seen in Ogg log files:
OGG-01232 receive TCP Params error: TCP/IP error 104 (Connection reset by peer ).

After checking Metalink, we probably talked about the relationship between extract and collector, which is divided into streaming and nostreaming modes, each with its own advantages. We recommend that you use the streaming mode if this error is not frequent. The original text is posted below:

OGG-01232 receive TCP Params error: TCP/IP error 104 (Connection reset by peer). (Document ID 1684527.1)

Go to the bottom

 

In this document Symptoms   Cause   Solution   Applies: Oracle goldengate-version 11.2.1.0.1 to 12.1.2.0.0 [release 11.2 to 12.1] Information in this document applies to any platform. Symptoms Gg extract/pump runs fine for hours or days and then the below error occurs, which causes the extract/pump to abend. This error occurs intermittently. Error OGG-01232 receive TCP Params error: TCP/IP error 104 (Connection reset by peer ). Network teams have found no informative errors in logs on either source or target boxes. Gg extract/pump has to be manually restarted.   Cause Extract/pump uses streaming mode by default Most of the TCP/IP errors are treated fatal and results in an immediate abend. I. e. OGG-01232 receive TCP Params error: TCP/IP error 104 (Connection reset by peer ).   In streaming mode communication between extract and the Collector is Asynchronous. Extract does not wait for an acknowledgement before sending Subsequent messages. When an error occurs in streaming mode, extract does Not know at which point it shoshould resend data, so an error is deemed fatal.   Solution Option 1: Use the nostreaming option if hitting TCP/IP errors too often In nostreaming Mode Communication Between extract and the Collector is Synchronous; extract can only send out new data after it has es Acknowledgement of the previous data from the collector. If an error occurs, Extract can simply resend the last transmission. Nostreaming-will make the data pump more resilient to transient network outages Option 2 Add autorestart to the Manager PRM File To have all pumps restart when it gets a TCP/IP Error Autorestart <process type>, retries..., waitminutes..., resetminutes .. I. e Autorestart extract *, retries 3, waitminutes 5, resetminutes 60   You will need to decide which values work best for you The GG reference has more details about the syntax. Oracle? Goldengate Windows and Unix Reference Guide 11g Release 2 Patch Set 1 (11.2.1.0.1) E29399-01 Oracle? Goldengate Reference for Oracle goldengate for Windows and Unix 12C (12.1.2) E29392-03

OGG-01232 receive TCP Params error: TCP/IP error 104 (Connection reset by peer ).