Consultor Eletrônico



Kbase P108124: Re-enabling replication after a failure condition.
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   9/15/2005
Status: Unverified

FACT(s) (Environment):

Fathom High Availability Replication 3.0A
Fathom High Availability Replication 10.0B

SYMPTOM(s):

How to re-enable replication after a failure condition.

FHAR 3.0A and 10.0B User's Guide refer to the steps in "Fathom Replication startup and initialization process" in order to (re) start replication after a forced shutdown of the Source or Target database.
Documentation is referring to the wrong chapter, it should refer to the "Starting Fathom Replication" chapter.

FIX:

The below instructions have been taken from Page 2-18, "Starting Fathom Replication".


Starting Fathom Replication:

To run Fathom Replication, start your source and target databases with a Fathom Replication qualifier (-DBService replserv or -DBService replagent). The startup order does not matter, but it is recommended if you did not set the defer-agent-startup property to a non-zero value in your server properties file, that you start your target database first, so that the Fathom Replication server does not time out.
If you start your source database first, the target database must be started before the connect-timeout property in the [control-agent.name] section of the server properties file expires.

Starting up the source database:
Use the following command to start the source database " PROSERVE -db source_db_name -DBService replserv " The -DBService argument instructs the broker to start the Fathom Replication server. Database activity cannot begin until Fathom Replication has completed its startup and initialization, unless you have used the defer-agent-startup property.

Any valid PROSERVE argument can be used to start the source database. When using arguments that affect shared memory (number of users, clients per server, maximum number of servers, etc.), you should be careful to use the same arguments and values when you start the target database. If there is a configuration error, the Fathom Replication server will be brought down even if th