An enterprise is distributing catalog information centrally stored on the mainframe in DB2 UDB to several satellite locations where subsets of the data are stored in Oracle for fast and easy access. Periodic corrections to the catalog information, gathered at the local offices, are replicated back to DB2 UDB.
The example uses Replication Agent for DB2 UDB, Replication Server, Replication Agent for Oracle, and the DirectConnect for z/OS Option to replicate between DB2 and Oracle.
ECDA Option for Oracle is a component of Enterprise
Connect Data Access.
Figure 3-3 illustrates this sample scenario.
Figure 3-3: Processing bidirectional replication between DB2 and other databases within the enterprise
As shown in Figure 3-3, DB2 UDB data is replicated by Replication Agent for DB2 UDB and sent to Replication Server, which passes the data to ECDA Option for Oracle. ECDA Option for Oracle passes the data to the Oracle database for storage. Corrections that have been made to the data on the Oracle database are replicated by Replication Agent for Oracle and sent through Replication Server, DirectConnect for z/OS Option, and DB2 UDB Option for CICS. DB2 UDB Option for CICS then sends the data to the DB2 UDB database for storage.
