Kbase P54900: Extracts from Fathom Replication V2.0A Release Notes
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
GOAL:
Extracts from Fathom Replication V2.0A Release Notes
FIX:
2.2. Processing If Fathom Replication Agent Failure Occurs
RN#: 10A1B102
If a Fathom Replication agent failure occurs, for example, the rpagent process ends abnormally, the only way to restart the agent is to restart the target database.
Under normal circumstances, the broker or watchdog process dynamically backs out active transactions for a process after that process unexpectedly ends. The dynamic back out process cannot be performed on behalf of the Fathom Replication agent because target database updates must always be driven from the source database. Dynamic back out does update the database.
In the event of an unexpected Fathom Replication agent failure, dynamic transaction back out does not occur and the target database is left in an inconsistent state. This could cause 4GL or SQL processes accessing the database to end abnormally. After the target database is restarted and synchronization is performed, all target database access should proceed normally.
2.14. Remote Agent Status On Server Side Remains Running If Agent Has Failed To Provide Latency Information
RN#: 20A229889
If the Fathom Replication Agent loses connection with the Fathom Replication Server for any reason, the Remote Agent Status in DSRUTIL MONITOR still provides information. This information is provided so that the user can take advantage of the new latency information. The way the Remote Agent Status displays whether the Fathom Replication agent has lost connection is through the State field in the Remote Agent Status display. Be sure to check the State field when using the DSRUTIL MONITOR function with Remote Agent Status, as this will tell you what state the agent is in and whether or not the Fathom Replication server is in contact with the agent.
2.19. The DSRUTIL canelDefer Action Is Allowed After Agent Startup
RN#: 20A229896
If you start the replication server with the defer-agent-startup parameter, the cancelDerfer DSRUTIL action can still be issued after the replication server has started the agent. There is no adverse affect and viewing the replication agent status or log file will confirm that the agent started successfully.