Question Live & Oer Connection Issue

Hello All,

We have one Live production server and one OpenEdge replication server. If connection fail between Live (Source) and OER (Target) server because of ERROR: - “(12688) The Replication Server has been terminated or the Source database has been shutdown. The Agents will enter PRE-TRANSITION, waiting for re-connection from the Replication Server.” Then we have to stop live production database and have to follow all the steps (including REPL backup/restore) that we had done earlier for creating OER server. This is a heavy loss of production downtime, is there any way to fix this issue without stopping live environment.

There is one other scenario of connection failure between Live and OER server that could be resolved by restarting server.

Kindly suggest.

Regards

You are over-reacting.

You shouldn't need to do anything more than restart the Live environment (if the db itself is still up you may just need to restart the replication server). The target should then notice that the source is back online.

You have not shared your Progress version or OS platform but OE Replication is famously "delicate" and it is very much to your advantage to stay up to date -- ancient, obsolete and unsupported releases like 9.1e or 10.1c are even worse places to be if you are running replication.

Hi Tom,

Thanks for your reply on this!!!

Live server is up but OER server is down from last few days. Restarting replication server (By command: - dsrutil source-db-name -C restart server) isn’t working because I think it will only work when both Live and OER servers are up and time gap of connection failure is very less.

Progress version: - 10.2B

Kindly suggest.

Regards

Are you telling me that it takes you multiple days to notice that your replication target has gone into pre-transition?

You need the ProTop Dashboard with the "monitoring and alerting" features enabled ProTop Monitoring and Alerting Service

What specific commands are you running and what error messages are they giving you?

Make sure you get better monitoring in place like Tom suggests. A replication target doesn't really help if it isn't live.

Posting the exact error messages and current state would be really helpful for us to help you.

If your target DB is able to be started.. make sure the agent is started before trying to restart the replication server.

Assuming your target DB is completely gone... here is a KB you can use as a guide to enable a new replication target with the source database online... Progress KB - What are the steps to enable OpenEdge Replication on a live database on OpenEdge 10.1B or later

I wouldn't suggest doing that until you give us more information though. There might be easier ways to fix this.