Manage Warm Standby Applications

Set up, configure, and monitor a warm standby application between two databases—the primary or active database and a single standby database.

Changes to the primary database are copied directly to the warm standby database. To change or qualify the data sent, you must add table and function replication definitions.

Replication Server supports setting up and managing warm standby applications for SAP ASE and Oracle databases. See Heterogeneous Warm Standby for Oracle in the SAP Replication Server Heterogeneous Replication Guide for detailed information on how to set up and configure a warm standby application between two Oracle databases.

You can also use multisite availability (MSA) to set up a warm standby application between SAP ASE databases. MSA enables replication to multiple standby and replicate databases. You can choose whether to replicate the entire database or replicate (or not replicate) specified tables, transactions, functions, system stored procedures, and data definition language (DDL). See SAP Replication Server Administration Guide Volume 1 > Manage Replicated Objects Using Multisite Availability.

• Warm Standby Applications
  A warm standby application is a pair of databases, one of which is a backup copy of the other. Client applications update the active database; Replication Server maintains the standby database as a copy of the active database.
• Replicated Information for Warm Standby
  SAP Replication Server supports different methods for enabling replication to the standby database. The level and type of information that SAP Replication Server copies to the standby database depends on the method you choose.
• Setting Up ASE Warm Standby Databases
  Setting up databases for a warm standby application involves several high-level tasks.
• Replication of the Master Database in a Warm Standby Environment for ASE
  There are several requirements and restrictions for replicating the master database in an Adaptive Server warm standby environment.
• Switch the Active and Standby ASE Databases
  You can switch to the standby database when the active database fails or when you want to perform maintenance on the active database.
• Monitor a Warm Standby Application
  You can use the Replication Server log file or several commands to monitor a warm standby application between two Adaptive Server databases or Oracle databases.
• Set up Clients to Work with the Active Data Server
  You must devise a method to switch client applications when you switch the active and standby databases in Replication Server using the switch active command, as Replication Server does not switch client applications to the new active data server and database automatically.
• Alter Warm Standby Database Connections
  Learn the options for reconfiguring or modifying the logical database connection and the physical database connections. Under ordinary circumstances, if you set up a warm standby application through the usual procedure, the default settings will work correctly.
• Warm Standby Applications Using Replication
  Learn about warm standby applications that involve replication, where the logical database serves as a primary or replicate database in the replication system.
• Replication Definitions and Subscriptions for Warm Standby Databases
  You can create replication definitions and subscriptions for warm standby applications.
• Loss Detection and Recovery
  Creating a warm standby application introduces additional types of loss detection messages into a replication system.