In this Document
APPLIES TO:
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 should 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 receives an
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
|