The following describes the Mirror Replication Agent communications for ASE and Oracle.
For network connections, Mirror Replication Agent uses the Java Database Connectivity (JDBC) protocol, as implemented by the Sybase JDBC driver, jConnect™ for JDBC™.
Each Mirror Replication Agent instance uses a single instance of jConnect for JDBC to communicate with all Open Client™ and Open Server™ applications, including the Adaptive Server® Enterprise (ASE) primary data server.
Mirror Replication Agent uses file or device I/O for access
to the mirror log devices.
Figure 1-6 shows how Mirror Replication Agent communicates with other Mirror Activator system components.
Figure 1-5: Mirror Replication Agent communications for ASE
During normal operation (while replicating transactions), Mirror Replication Agent maintains continuous connections with the following Mirror Activator system components:
Primary data server
Replication Server
Mirror Replication Agent maintains a connection with the primary data server to reserve the logscan context, which gives it control of the secondary truncation point in the primary database transaction log.
Depending on its configuration, Mirror Replication Agent may connect to the Replication Server System Database (RSSD) to retrieve replication definitions, which it can use to process the replicated transactions more efficiently.
Mirror Replication Agent uses the JDBC drivers supplied by Oracle for all communications with Oracle.
Each Mirror Replication Agent instance uses a single instance of the JDBC driver to communicate with the primary data server. The Sybase jConnect JDBC driver is used to communicate to all Open Client and Open Server applications.
Mirror Replication Agent uses file or device I/O for access
to the mirror log devices.
Figure 1-6 shows how Mirror Replication Agent communicates with other Mirror Activator system components.
Figure 1-6: Mirror Replication Agent communications for Oracle
During normal operation (while replicating transactions), Mirror Replication Agent maintains continuous connections with the following Mirror Activator system components:
Primary database
Primary Replication Server
Mirror Replication Agent maintains a connection with the primary data server to perform primary database log truncation activities.
Depending on its configuration, Mirror Replication Agent may connect to the RSSD to retrieve replication definitions, which it can use to process the replicated transactions more efficiently.
