Kbase P37242: Cannot start replication with SQL92 primary broker on target database
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/15/2008 |
|
Status: Verified
FACT(s) (Environment):
Progress 9.1D
Fathom High Availability Replication 1.0A
Fathom High Availability Replication 2.0A
SYMPTOM(s):
Cannot start replication with SQL92 primary broker on target database
Unable to synchronize Fathom Replication
Replication server unable to connect to replication agent
Target database is configured to have 2 brokers, SQL92 and 4GL
Connection failure for service prosv08 host <hostname> transport TCP. (5483)
Connections to this database will not be allowed until all Database Services started have completed their startup and initialization. (10545)
The Site Replication Server cannot connect to the database broker on <hostname> at the port -1. (10396)
The connection attempt to the Site Replication Agent agent1 failed. (10397)
The Site Replication Server could not connect to any agents.
The Site Replication Server is ending. (10505)
CAUSE:
The target database has it's primary broker defined as SQL only. Connections to target database are not allowed until the replication gets synchronized via a connection from the replication server to the replication agent. Since the replication server needs to connect to the replication agent via a "4GL" broker port, connection are never allowed to the source. The replication server terminates as well.
FIX:
Define the target database's primary broker as 4GL Only and it's secondary broker as SQL only.