In a hot standby application, a standby database can be placed into service without interrupting client applications and without losing any transactions. A hot standby database guarantees that transactions committed on the active database are also committed on the standby. When both databases are up, the active database and the standby database are in sync, and the hot standby database is ready for immediate use.
Alternately, a warm standby application maintained by Replication Server:
Can be used in environments where data mirroring applications cannot, especially when necessary hardware is not available.
Tolerates temporary network failures better than some hot standby applications because committed transactions can be stored on the active database, even when the standby database is down.
Minimizes overhead on the active database because the active database does not need to verify that the databases are in sync.
However, a warm standby application maintained by Replication Server also:
Requires some interruption of client applications when switching to the standby database.
May not have executed in the standby database the most recent transactions committed in the active database.
