Non-ASE Primary to Non-ASE Replicate

The Non-ASE primary to Non-ASE replicate scenario varies in complexity, depending on the mix of non-ASE data servers.

Replication System Components

The following components are required for a non-ASE primary to non-ASE replication configuration:

Non-ASE primary data server. For example, Oracle.
Replication Agent designed for the primary data server. For example, Replication Agent for Oracle.
Replication Server.
ExpressConnect (for Oracle or HANA DB) to replicate to Oracle or HANA DB, or a relevant ECDA database gateway designed for the replicate data server, such as the ECDA Option for ODBC for Microsoft SQL Server.
Non-ASE replicate data server. For example, Microsoft SQL Server.

Consider the following issues in a non-ASE primary to non-ASE replicate configuration:

The Replication Server primary database connection may require a valid user ID and password for the primary database. This user ID must have authority to apply replicate transactions (even if no transactions will be replicated to the primary database).
To use direct-load materialization, you must create the connection to the primary database using the appropriate connection profile: rs_rs_to_oracle_ra, rs_rs_to_mssql_ra, rs_rs_to_udb_ra, or rs_rs_to_hanadb_ra.
The Replication Server replicate database connection must be created using the correct profile for the primary and replicate database. The connection profile specifies the correct function string classes and error classes for the replicate database, and additionally may contain class-level translation definitions and replicate database object creation, to support replication.