Scenario: Distributing enterprise data between multiple central databases

A large regional supplier maintains its enterprise data in a central database in Sacramento. The company then merges with a second regional supplier of comparable size in Denver. The Sacramento enterprise maintains its data on an Oracle system, but the Denver enterprise uses Adaptive Server Enterprise (ASE). To circumvent the lengthy and expensive process of migrating data in either location to another platform, both organizations implement an integrated, bidirectional replication system

To set up bidirectional, enterprise-wide replication, the Sacramento and Denver enterprises use these components because it is preferable, although not mandatory:

The Replication Agent for Oracle and ECDA Option for Oracle are installed at the Sacramento location where Oracle is installed.

NoteAccess to ASE in Denver is required, however ASE is not included in RSHE.

Figure 3-1 illustrates the sample scenario that integrates Oracle data in Sacramento with ASE data in Denver. In this case, the Replication Server acts as both the primary Replication Server and the replicate Replication Server.

Figure 3-1: Bidirectional, enterprise-wide replication

This figure illustrates a bidirectional, enterprise-wide heterogenous replication using the various RSHE components.