If you are unaware that Replication Server has stopped running, the database environment may become corrupted. If the Adaptive Server fails and the RCM attempts to connect to Replication Server, which also fails, the standby server is out of date because there was a period of time during which the Replication Server was down and not replicating transactions to the standby server.
Attempts to add transactions to the standby server at this point might fail, and, as a result, the entire database environment could be out of date. In this case, the RCM still switches users to the standby environment to ensure that current transactions are being captured. If the entire database environment becomes out of date, you must recover from backup, following your internal procedure for recovery.
See “Managing a Warm Standby Applications” in Replication Server Administration Guide, Volume 2 for more information about transaction processing in a warm standby environment.
