IBM DB2 for Linux, UNIX, and Windows as Replicate Data Server

Learn about the primary database issues and considerations specific to the DB2 UDB data server for Linux, UNIX, and Windows in an SAP replication system.

For information about basic replication system administration, see the Replication Server Administration Guide Volume 1.

• DB2 UDB Replicate Data Servers
  As a replicate data server in a replication system, the DB2 UDB interacts with the ECDA Option for ODBC database gateway.
• Replication Intrusions and Impacts in DB2 UDB
  The only significant intrusions or impacts to the DB2 UDB replicate database are the database objects that are created by the connection profile that creates three tables in the replicate database to support Replication Server operations
• DB2 UDB Replicate Database Permissions and Limitations
  Replication Server requires a maintenance user ID that you specify using the Replication Server create connection command to apply transactions in a replicate database.
• Connectivity for DB2 UDB Replicate Database
  A Replication Server database connection name is made up of two parts: a data server name (server_name) and a database name (db_name). The server_name is the name of the ECDA Option for ODBC database gateway server, and the db_name is the name of the DB2 UDB replicate database.
• DB2 UDB Replicate Database Configuration
  The heterogeneous datatype support (HDS) feature of Replication Server provides configuration information that allows you to set up the HDS feature in the replicate Replication Server and the DB2 UDB replicate database.
• Parallel DSI Threads for IBM DB2 Replicate Database
  In a heterogeneous replication environment, parallel DSI must ensure that the commit order in the replicate database is same as in the primary database. DSI can then resolve deadlock conflict, when deadlock has occurred, and Replication Server can rollback transactions and execute again.