OGG-01232 Receive TCP Params Error: TCP/IP Error 104 (Connection Reset By Peer).

经常在OGG日志文件中看到如下错误:

查了metalink,大概说的是extract 和collector 交互的关系,分为STREAMING 和NOSTREAMING 模式,各有各的优势。总的建议如果该错误不是很频繁,建议使用STREAMING模式。下面贴出原文:

OGG-01232 Receive TCP Params
Error: TCP/IP Error 104 (Connection Reset By Peer). (文档 ID 1684527.1)
转到底部


In this Document

Symptoms
  Cause
  Solution

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

时间: 2024-10-29 04:08:17

OGG-01232 Receive TCP Params Error: TCP/IP Error 104 (Connection Reset By Peer).的相关文章

OGG-01232 Receive TCP params error: TCP/IP error 104 (Connection reset by peer), endpoint:

源端: 2015-02-05 17:45:49 INFO OGG-01815 Virtual Memory Facilities for: COM anon alloc: mmap(MAP_ANON) anon free: munmap file alloc: mmap(MAP_SHARED) file free: munmap target directories: /home/ggt/goldengate/dirtmp. CACHEMGR virtual memory values (may

在VMware8.0.4安装centos6.3出现蓝屏,显示“anaconda: Fatal IO error 104 (Connection reset by peer) on X server :1.0. install exited abnormally [1/1]”?

解决方案:在创建虚拟机时选择“自定义(高级)”,然后点击“下一步”,在弹出的对话框中,在硬件兼容性该项选择 Workstation6.5-7.x.如果创建虚拟机时选择“标准”,默认的硬件兼容性将是Workstation8.0,就会报错.

TNS-12547 Linux Error: 104: Connection reset by pe (转载)

TNS-12547 Linux Error: 104: Connection reset by peer 解决过程参考:http://blog.chinaunix.net/u/7121/showart_403812.html [[email protected] log]$ lsnrctl startLSNRCTL for Linux: Version 10.2.0.1.0 - Production on 23-JUN-2009 09:53:26 Copyright (c) 1991, 2005

connection reset by peer, socket write error问题分析

上次写<connection reset by peer, socket write error问题排查>已经过去大半年,当时把问题"敷衍"过去了. 但是此后每隔一段时间就会又想起来,baidu.google一番,可能也会再拉周围的人小讨论一下,然后无果而终.淡忘,想起,淡忘,又想起,挥之不去. 这个周末它又在脑海中浮现,这次总算理解了这个问题,答案就在一本买了很久的新书<HTTP权威指南>中.如果懒得看下面的啰嗦,可以去直接看书中的<4.7.4 正常关闭

老项目采用tomcat出现异常:Connection reset by peer: socket write error 异常解决方法

项目一段时间就出现异常,导致无法登陆系统,数据库无法连接上 异常信息如下: java.sql.SQLException: Io 异常: Connection reset by peer: socket write error at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134) at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179) a

docker exec failed!!error from pipe caused \&quot;read parent: connection reset by peer\&quot;问题

一.复现报错: docker exec -it  wsqtest  bash rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "process_linux.go:110: decoding init error from pipe caused \"read parent: connection res

Jenkins Publish over SSH 异常:Connection reset by peer: socket write error

Jekins持续集成: 服务器时windows服务器: windows安装openssh服务: 安装包:https://github.com/PowerShell/Win32-OpenSSH/releases 开箱即用:步骤1 文件解压至C:\Program Files\OpenSSH 2 控制台cd至目录 3 执行powershell.exe -ExecutionPolicy Bypass -File install-sshd.ps1 启动服务ssh; 踩坑的地方:当时没有把文件放到C:\Pr

Jmeter遇到线程链接被重置(Connection reset by peer: socket write error)的解决方法

做性能测试的时候遇到一个很奇怪的问题,多线程的计划,有一个线程第一次能跑过,第二次确跑不过,单独跑这个线程跑多少次都没有问题,把思考时间改短也没有问题,唯独出现在特定的状态下,特定状态是啥,也不得而知,反正是几个设置叠加再一起碰巧出现...我就郁闷了...墙外的朋友貌似都有人遇到,墙内的没搜到,所以写了这样一篇文章简单记录一下,解决方法: 现象如图 第一次成功,第二次失败,所以错误率是50% 取样器的结果是这样的: 具体的错误信息: 看上去像是jmeter的bug,百思不得其解.google之.

解决error104 connection reset by peer;socket error问题

这个问题原因有两个: 1.因为你访问网站太多次,所以被网站管理员给禁止访问了. 解决方法: 1.延长time.sleep时间 2.设置代理 2.根本没有这个网站.(打开链接检查一下!!!)