Why are the TCP retries Longer Than the Time Specified in TCPERRs ? (Doc ID 1325124.1)

Last updated on JANUARY 15, 2017

Applies to:

Oracle GoldenGate - Version 5.0.0 and later
Information in this document applies to any platform.

Symptoms

2011-05-23 16:56:53 WARNING OGG-01223 TCP/IP error 10060 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.).

2011-05-23 16:57:25 WARNING OGG-01223 TCP/IP error 10060 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.).

2011-05-23 16:57:56 WARNING OGG-01223 TCP/IP error 10060 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.).
  • The TCPERRs file specifies 10 seconds as the wait interval for this error (and 3 retries).
  • Note that this is a sample. Similar behaviour is expected with other TCP error return codes.
#
# TCP/IP error handling parameters
#
# Default error response is abend
#

# Error Response Delay (csecs) Max Retries

ECONNABORTED RETRY 1000 10
#ECONNREFUSED ABEND 0 0
ECONNREFUSED RETRY 1000 12
ECONNRESET RETRY 500 10
ENETDOWN RETRY 1000 3
ENETRESET RETRY 1000 10
ENOBUFS RETRY 100 60
ENOTCONN RETRY 100 10
EPIPE RETRY 500 10
ESHUTDOWN RETRY 1000 10
ETIMEDOUT RETRY 1000 10
NODYNPORTS RETRY 100 10

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms