Functionality Enhancements

Enterprise Replication for Dynamic Server, Version 10.0, includes the following functionality enhancements:

• Event Alarms

  You can use event alarms that are specific to Enterprise Replication to automate many administrative tasks. See Enterprise Replication Event Alarms for more information.

• Master Replicates

  To guarantee consistency between the nodes in your Enterprise Replication environment, you can create master replicates. See Defining Master Replicates for more information.

• Templates

  Enterprise Replication provides templates to allow easy set up and deployment of replication for clients with large numbers of tables to replicate. See Using Templates to Set Up Replication for more information.

• Alter Support

  You can alter a replicated table's schema or its fragmentation strategy without stopping replication. See Performing Alter Operations on Replicated Tables for more information.

• 4Repair and Consistency Checking 4

  If replication has failed 4for some reason and data is inconsistent, you can synchronize your tables 4while replication is still active. You can also check the consistency of the 4replicate and optionally repair any inconsistent rows.

  4

  See Resynchronizing Data Among Replication Servers for more information.

• Initial Data Synchronization

  You can perform an initial synchronization when you start a replicate or replicate set to synchronize a new replicate, or add a new participant to an existing replicate.

  See Initially Synchronizing Data Among Database Servers for more information.

• Repair using ATS and RIS files

  You can also repair data after replication has failed by using ATS and RIS files. Enterprise Replication examines the specified ATS or RIS file and attempts to reconcile the rows that failed to be applied. This method is fast, but does not allow you as much flexibility in defining how the repair should be done. See Repairing Failed Transactions with ATS and RIS Files for more information.

• Shadow Replicates

  Enterprise Replication uses shadow replicates to manage alter and repair operations on replicated tables. If you perform manual remastering of a replicate that was defined with the -n option, you must create a shadow replicate. See Defining Shadow Replicates for more information.