OGG-01224 Address already in use
2017-05-24 10:35
120 查看
1, 启动manager也启动不了,会出现这个错误
[html] view
plaincopy
2013-01-03 06:28:58 ERROR OGG-01224 Address already in use.
2013-01-03 06:28:58 ERROR OGG-01668 PROCESS ABENDING.
说明原来的 Golden Gate 的Manager进程还在工作,占用了端口,
运行下面命令,就可以找到它,然后使用 kill -9 process_id 杀掉,这时就可以启动Manager进程了
ps -ef | grep mgr
2,启动mgr进程之后,运行命令 info all 发现所有进程都 abended 了,所以运行 start * 启动所有进程,过了一会,发现除了replicat进程,extract和data dump进程全部abended了,因为replicat进程是只读进程,利用同样的参数文件运行的replicat进程,Golden Gate不会认为它们有什么威胁,所以全部正常启动,但其实你利用 ps -ef | grep replicat可以看到很多重复的replicat进程,不过以前的replicat进程应该不工作了。
不过小心!!!很有可能原来的replicat进程还没有检测到异常,而新的进程报错,认真检查会出现以下现象:
a,使用info all 该进程是正常 running,但是使用 info process_name 指定该进程的时候,可以看到状态是abended.
b,使用view report replicat_process_name可以看到出错信息如下:
[plain] view
plaincopy
2013-01-06 23:39:59 ERROR OGG-00446 Unable to lock file "/u01/ggate/dirchk/replicat_tab5.cpr" (error 11, Resource temporarily unavailable). Lock current
y held by process id (PID) 27946.
3,利用 view report extract_process_name 可以看到以下错误消息
[plain] view
plaincopy
2013-01-03 06:42:19 ERROR OGG-01454 Unable to lock file "/ggdata/extract/dbservice1/schema1/t0000006" (error 11, Resource temporarily unavailable). Lock currently held by process id (PID) 26654.
2013-01-03 06:42:19 ERROR OGG-01668 PROCESS ABENDING.
说明,现在已经有一个PID在锁住当前这个文件,只要杀掉 26654这个进程,就能再次启动了,如此循环,把所有 extract的进程都启动
4, 利用view report dump_process_name 可以看到以下错误消息
[plain] view
plaincopy
2013-01-03 07:04:45 ERROR OGG-01031 There is a problem in network communication, a remote file problem, encryption keys for target and source do not matc
h (if using ENCRYPT) or an unknown error. (Reply received is Unable to open file "/ggdata/extract/dbservice1/schema1/t0000006" (error 11, Resource
temporarily unavailable)).
2013-01-03 07:04:45 ERROR OGG-01668 PROCESS ABENDING.
说明dump无法打开目标端的文件,查看目标段的 ggserr.log可以看到以下信息
[plain] view
plaincopy
2013-01-03 06:37:59 WARNING OGG-01223 Oracle GoldenGate Collector for Oracle:
Unable to lock file "/ggdata/extract/dbservice1/schema1/t000006" (error 11, Resource temporarily unavailable).
Lock currently held by process id (PID) 16795.
很明显,这个文件被目标段的进程所占用
[plain] view
plaincopy
[ggate@jabtl1001 ~]$ ps -ef | grep 16795
ggate 16795 29198 0 2012 ? 00:01:19 ./server -w 300 -p 7000-9000 -m 7810 -k -l /u01/ggate/ggserr.log
ggate 23567 20017 0 07:31 pts/4 00:00:00 grep 16795
可以看出是目标段的server进程在保护这个文件,启动data dump的时候,目标段会再启动一个文件对其进行写入,这时就产生冲突了。
所以需要把这个子进程杀掉即可 kill -9 16795
这时data dump的process 应该可以启动了
实际上,不能确定现在他们就能正常通信或者复制数据了。还是需要再测试一下,因为很可能会出现两种情况
a, 该抓取的已经抓取了,现在重新启动的extract process会不会重新抓取?所以要看情况是否需要修改其 begin now
b, data dump和extract的合作出现某些问题,和目标端的replicat的合作也出现了某些问题,这时文件号很可能不一致,需要具体情况具体分析。
[html] view
plaincopy
2013-01-03 06:28:58 ERROR OGG-01224 Address already in use.
2013-01-03 06:28:58 ERROR OGG-01668 PROCESS ABENDING.
说明原来的 Golden Gate 的Manager进程还在工作,占用了端口,
运行下面命令,就可以找到它,然后使用 kill -9 process_id 杀掉,这时就可以启动Manager进程了
ps -ef | grep mgr
2,启动mgr进程之后,运行命令 info all 发现所有进程都 abended 了,所以运行 start * 启动所有进程,过了一会,发现除了replicat进程,extract和data dump进程全部abended了,因为replicat进程是只读进程,利用同样的参数文件运行的replicat进程,Golden Gate不会认为它们有什么威胁,所以全部正常启动,但其实你利用 ps -ef | grep replicat可以看到很多重复的replicat进程,不过以前的replicat进程应该不工作了。
不过小心!!!很有可能原来的replicat进程还没有检测到异常,而新的进程报错,认真检查会出现以下现象:
a,使用info all 该进程是正常 running,但是使用 info process_name 指定该进程的时候,可以看到状态是abended.
b,使用view report replicat_process_name可以看到出错信息如下:
[plain] view
plaincopy
2013-01-06 23:39:59 ERROR OGG-00446 Unable to lock file "/u01/ggate/dirchk/replicat_tab5.cpr" (error 11, Resource temporarily unavailable). Lock current
y held by process id (PID) 27946.
3,利用 view report extract_process_name 可以看到以下错误消息
[plain] view
plaincopy
2013-01-03 06:42:19 ERROR OGG-01454 Unable to lock file "/ggdata/extract/dbservice1/schema1/t0000006" (error 11, Resource temporarily unavailable). Lock currently held by process id (PID) 26654.
2013-01-03 06:42:19 ERROR OGG-01668 PROCESS ABENDING.
说明,现在已经有一个PID在锁住当前这个文件,只要杀掉 26654这个进程,就能再次启动了,如此循环,把所有 extract的进程都启动
4, 利用view report dump_process_name 可以看到以下错误消息
[plain] view
plaincopy
2013-01-03 07:04:45 ERROR OGG-01031 There is a problem in network communication, a remote file problem, encryption keys for target and source do not matc
h (if using ENCRYPT) or an unknown error. (Reply received is Unable to open file "/ggdata/extract/dbservice1/schema1/t0000006" (error 11, Resource
temporarily unavailable)).
2013-01-03 07:04:45 ERROR OGG-01668 PROCESS ABENDING.
说明dump无法打开目标端的文件,查看目标段的 ggserr.log可以看到以下信息
[plain] view
plaincopy
2013-01-03 06:37:59 WARNING OGG-01223 Oracle GoldenGate Collector for Oracle:
Unable to lock file "/ggdata/extract/dbservice1/schema1/t000006" (error 11, Resource temporarily unavailable).
Lock currently held by process id (PID) 16795.
很明显,这个文件被目标段的进程所占用
[plain] view
plaincopy
[ggate@jabtl1001 ~]$ ps -ef | grep 16795
ggate 16795 29198 0 2012 ? 00:01:19 ./server -w 300 -p 7000-9000 -m 7810 -k -l /u01/ggate/ggserr.log
ggate 23567 20017 0 07:31 pts/4 00:00:00 grep 16795
可以看出是目标段的server进程在保护这个文件,启动data dump的时候,目标段会再启动一个文件对其进行写入,这时就产生冲突了。
所以需要把这个子进程杀掉即可 kill -9 16795
这时data dump的process 应该可以启动了
实际上,不能确定现在他们就能正常通信或者复制数据了。还是需要再测试一下,因为很可能会出现两种情况
a, 该抓取的已经抓取了,现在重新启动的extract process会不会重新抓取?所以要看情况是否需要修改其 begin now
b, data dump和extract的合作出现某些问题,和目标端的replicat的合作也出现了某些问题,这时文件号很可能不一致,需要具体情况具体分析。
相关文章推荐
- ###Address already in use: 总是提示8080占用,原因:【pom.xml配置的启动端口必须是tomcat7:run才行,tomcat:run默认总是8080端口!】
- Address already in use的疑问
- 服务器部署多个tomcat(Address already in use: JVM_Bind)
- tomcat错误严重: StandardServer.await: create[8005]: java.net.BindException: Address already in use: JVM_
- nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) 错误解决
- android 跨进程通信 LocalServerSocket LocalSocket Address already in use
- SpringBoot项目调试时出现java.net.BindException: Address already in use: bind
- nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) 错误解决
- Unable to open debugger port (127.0.0.1:63777): java.net.BindException "Address already in use: JVM
- tomcat启动不了——Error initializing endpoint——java.net.BindException: Address already in use: JVM_Bind <n
- Address already in use: JVM_Bind解决办法之一
- ActiveMQ启动报 Address already in use: JVM_Bind
- 解决Address Already in use : JVM_Bind错误
- Error running Tomcat8: Address localhost:1099 is already in use 错误解决
- address already in use
- [spring boot][异常处理] java.net.BindException: Address already in use: bind
- apache启动报错(98)Address already in use: make_sock: could not bind to address [::]:80
- java.net.BindException: Address already in use: JVM_Bind
- Unable to open debugger port : java.net.BindException "Address already in use: JVM_Bind(IDEA13.0)
- tomcat端口冲突解决 Address already in use: JVM_Bind <null>:8080