Kbase P128295: Secondary login broker started against target database disconnects with message 2525
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/17/2008 |
|
Status: Verified
FACT(s) (Environment):
Fathom High Availability Replication 3.0A
Fathom High Availability Replication 10.X
Windows
SYMPTOM(s):
Progress Explorer is unable to start secondary broker against target database
You are not licensed to access the database. (10830)
The primary login broker cannot be set to SQL only login broker
Replication agent cannot connect if 4GL connections are not allowed to the primary login broker
Replication is in sync when the secondary login broker is started with a script against the target database
The secondary login broker is started with a user account
SQL connection can be established whilst the SQL Broker is running
When SQL Broker shuts down SQL connections receive "Socket Closed" error
Disconnecting dead server 1 (2525)
CAUSE:
Bug# OE00127281
FIX:
Upgrade to OpenEdge 10.1B where secondary login brokers are allowed to run as part of a limited login database.
Workaround:
NOTE: This particular issue is not a direct consequence of the fix in 10.1B, but a matter of how a workaround has been implemented when needing to start a secondary login broker against the target database (which cannot run in versions prior 10.1B directly from the Progress Explorer environment when the target database is started)
1. Make sure that the replication is sync before issuing the startup of the secondary login broker.
Parse for the following entries in the database lg files:
(10668) The Source and Target databases are synchronized.
(10490) Fathom Replication Agent agent1 is beginning normal processing at block 0.
Alternatively, verify through "dsrutil target -C status agent1 -detail" a return code of 3049 indicates that Normal Processing has suceeded post synchronisation.
For Status return-codes, please refer to the version specific "OpenEdge Replication User Guide", Reference, DSRUTIL status qualifier.
2. Use a bat file to startup the secondary login broker then add that .bat file as a service (started as system account). In this way the secondary login broker, running outside the AdminService, will not terminate when the user account starting the .bat file, logs off the system.
proserve target -ServerType SQL -m3 -S 4505 -Mpb 6 -Mi 1 -Ma 2
3. (Optional) Modify the SGStartupDelay parameter. This parameter is a timing value for database startup. The default is 2 seconds. Increasing this parameter will allow more time for the startup for the database and it's related processes.
Steps for modifying database startup timing value:
a. Create a file to contain the modified parameter. For example delaydbinit.txt. The file should contain the line SGStartupDelay=n. Where n = time in seconds, eg: SGStartupDelay=10. Save this file in the Progress working directory.
b. Edit the %DLC%/properties/AdminServerPlugins.properties file.
Find the section [PluginPolicy.Progress.AdminServer].
At the end of the section find the jvmargs=<arguements>
Add: -DConfigToolTimings=<filename>
Example of modification: jvmargs=-DConfigToolTimings=delaydbinit.txt
c. Restart the AdminServer for the new settings to take effect.