stoperp

9 积分	0 好友	3 主题

发消息

OGG中trail传输问题

1^#

发表于 2011-11-1 21:11:50 | 查看: 8039| 回复: 8

我现在goldengate的模式为1对2的模式

1：源端--目标端1（ mgr端口分别为7089--7089，内网，无防火墙设置）

2：源端--目标端2 (mgr端口分别为7089-7090，远程异地传输，有防火墙设置，端口号7089，,7090已开启）

目:前 1传输正常，trail能正常传过去并且应用

2的pump传输进程状态是running,但是trail文件传不过去。是不是goldengate除了7090，还要开启其他的端口号

分享0

收藏0 回复只看该作者道具举报

Liu Maclean(刘相兵

2^#

发表于 2011-11-1 21:13:32

pump 的日志？

回复只看该作者道具举报

stoperp

3^#

发表于 2011-11-1 21:22:24

回复 2# 的帖子

pump进程状态是running,report里面没有报错信息
report报告的具体内容明天加载上来。

回复只看该作者道具举报

xifenfei

4^#

发表于 2011-11-1 22:33:30

需要打开一串端口，而不是只开一个主进程端口就可以了以前遇到过，长时间的runing后，会出现tcp不能连接的提示

回复只看该作者道具举报

stoperp

5^#

发表于 2011-11-2 09:27:32

还需要开启哪些端口呢？

因为现在我的目标机已经放置到异地的一个机房里面了。，机房是有防火墙的，对方只给我们开通了7090、7089端口。

回复只看该作者道具举报

Maclean Liu(刘相兵

6^#

发表于 2011-11-2 14:16:19

OGG Extract Pump abended with ERROR OGG-01224 TCP/IP error 110 (Connection timed out); retries exceeded

Applies to:

Oracle GoldenGate - Version: 4.0.0 and later [Release: 4.0.0 and later ]
Information in this document applies to any platform.
Symptoms

Pump Extract abend with the following error:

ERROR OGG-01224 TCP/IP error 110 (Connection timed out); retries exceeded.

Cause

This is generally due due to basic issues like:

* The remote manager process is not running or is running with incorrect port number

*The RMTHOST parameter in the pump extract is not configured correctly.

In other cases, the issue could be due to firewalls that forbid the connection, blocking certain ports or
processes. This is generally seen when there is a firewall between the source and target machine and either the ports are not open or just the manager port is open.

Solution

The Extract, Replicat and Ggsci processes use ports normally starting at port 7840 and ascend sequentially. The ggsci command 'send manager getportinfo detail ' will retrieve the current list of ports that have been allocated by Manager and their corresponding process IDs.

If you have some port restrictions, then you could use the DYNAMICPORTLIST with some range so that the collector process will allocate the ports from that range.

In general to overcome this issue, we could do something like below

1)Change the target manager parameter file to use something like the following

port 7809
dynamicportlist 7810-7820

2. Stop and start the manager
3.Open ports 7809 through 7820 in the firewall
4. Re-start the source pump

The port range used in dynamicportlist(7810-7820) and the manager port 7809 is just an example. You can define your own ports there and have them open.

回复只看该作者道具举报