Stop replicate times error:opening port for Replicat myrep (TCP/IP error:connection refused).
Start replicate times Replicat xxx is already running.
The reason is that the corresponding xxx.pcs file in the Dirpcs directory is not deleted properly.
Workaround: Delete the PCs file and check for deletion permissions.
Here is an article referring to a foreign country:
We Use the 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 UNRESPO Nsive. Even stranger, deleting and recreating the rep gave the same Result-before I even attempted to start the rep for the Fir St time, it said "starting", and an attempt-to-start it gave me "Process is starting Up-try again-later".
the cause is the REP process status file, located in the Dirpcs folder under the Goldengate Root-there should is a file for each REP, that's currently running giving details about the status. When a REP stops, the 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 s Hould has 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 this, but once started again, they all worked without issue. I hope this saves your the troubleshooting time of hunting down these files!
Oracle Goldengate Replicat startup Times is running a workaround