惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
L
Lohrmann on Cybersecurity
aimingoo的专栏
aimingoo的专栏
V
V2EX
S
Security Affairs
T
Threatpost
C
CXSECURITY Database RSS Feed - CXSecurity.com
IT之家
IT之家
J
Java Code Geeks
The Register - Security
The Register - Security
U
Unit 42
C
CERT Recently Published Vulnerability Notes
月光博客
月光博客
A
About on SuperTechFans
H
Hackread – Cybersecurity News, Data Breaches, AI and More
T
The Blog of Author Tim Ferriss
Cisco Talos Blog
Cisco Talos Blog
Project Zero
Project Zero
S
Schneier on Security
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
D
DataBreaches.Net
博客园 - 司徒正美
V
Vulnerabilities – Threatpost
T
Tor Project blog
Security Latest
Security Latest
T
The Exploit Database - CXSecurity.com
T
Threat Research - Cisco Blogs
Scott Helme
Scott Helme
Application and Cybersecurity Blog
Application and Cybersecurity Blog
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
M
MIT News - Artificial intelligence
云风的 BLOG
云风的 BLOG
小众软件
小众软件
L
LangChain Blog
Attack and Defense Labs
Attack and Defense Labs
Recent Commits to openclaw:main
Recent Commits to openclaw:main
P
Palo Alto Networks Blog
A
Arctic Wolf
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
C
Cyber Attacks, Cyber Crime and Cyber Security
博客园 - 叶小钗
D
Darknet – Hacking Tools, Hacker News & Cyber Security
L
LINUX DO - 最新话题
MongoDB | Blog
MongoDB | Blog
Webroot Blog
Webroot Blog
H
Hacker News: Front Page
Know Your Adversary
Know Your Adversary
Spread Privacy
Spread Privacy
AWS News Blog
AWS News Blog
Engineering at Meta
Engineering at Meta

博客园 - jimeper

RAC升级后,一个节点无法连接数据库,报ORA-12537: TNS:connection closed 升级到11.2.0.4后用srvctl无法启用数据库实例,报CRS-0254: authorization failure Oracle 11gR2 RAC DBCA无法识别ASM磁盘组(ORA-19504,ORA-15045,ORA-17502,ORA-15081) Troubleshooting Scheduler Autotask Issues (Doc ID 1561498.1) LINUX系统下添加映射存储LUN goldengate一些参数整理 原创:goldengate从11.2升级到12.1.2 Transaction recovery: lock conflict caught and ignored 搭建mongodb集群(副本集+分片) 不停止MySQL服务增加从库的两种方式 Oracle 11g RAC环境下Private IP修改方法及异常处理 LOB字段存放在指定表空间 清理CLOB字段及压缩CLOB空间 (原创)INTERVAL分区表与RANGE分区表相互转化 删除数据报ORA-00600: internal error code, arguments: [ktbesc_plugged] OGG-03517 Conversion from character set failed解决方法 Redis之高可用方案 linux中shell变量$#,$@,$0,$1,$2的含义解释 Logdump使用指引 用飞信监控GoldenGate进程
Oracle Goldengate REPLICAT启动时报正在运行解决办法
jimeper · 2016-03-19 · via 博客园 - jimeper

stop replicate时报ERROR: opening port for REPLICAT MYREP (TCP/IP error: Connection refused).

start replicate时报REPLICAT xxx is already running.

原因是dirpcs目录下对应的xxx.pcs文件没有正常删除。

解决办法:删除pcs文件,检查是否有删除权限。

以下是引用国外的一篇文章:

We use Oracle Goldengate to replicate data from an Oracle database into a SQL Server. However, I got an alert the other day that replication had stopped, and when I checked the status of replication, all the REPs we had set up were in status "Starting...", but none we actually doing anything.

Attempting to stop them got the following error:

GGSCI (GGSERVER) 68> stop rep MYREP

Sending STOP request to REPLICAT MYREP ...

ERROR: opening port for REPLICAT MYREP (TCP/IP error: Connection refused).

OR

GGSCI (GGSERVER) 68> start replicat REPYL01C

REPLICAT REPYL01C is already running.

Stopping/Starting the manager service or rebooting the PC didn't help either - they still said "Starting" and were unresponsive. Even stranger, deleting and recreating the REP gave the same result - before I even attempted to start the REP for the first time, it said "Starting", and an attempt to start it gave me "Process is starting up - try again later".

The cause was the REP process status file, located in the DIRPCS folder under the Goldengate root - there should be a file for each REP that's currently running giving details about the status. When a REP stops, this file is deleted. Since all of the current REPs weren't doing anything (they were all sitting at the end of the previous trail file), they should have been stopped. I deleted the PCR files for the affected REP streams, and then manager reporting "STOPPED" - at that point, I was able to start up each REP without issue.

I'm not sure how they got that way, but once started again, they all worked without issue. I hope this saves you the troubleshooting time of hunting down these files!