Database Replication - Recreating Publications and Subscriptions in IBM i2 iBase

Answer

Recreating publications
Creating publications for the database that contains the entity and link data is the same regardless of whether the database was previously enabled for replication or not. For detailed information, see Publishing Entity and Link Data.

How to recreate a subscription
When recreating subscriptions, you should not need to generate a snapshot containing the data and schema because the databases should already have all the data. The iBase administrator should have denied database access to all users until replication is reconfigured. The databases will have the complete database schema— if there were any schema changes, the iBase administrators will have applied the changes by using the appropriate iBase utility.

Start a new subscription, either a push or a named pull subscription. The subscription should be as follows:

Select

• The Subscriber has the schema and data.
• The Merge Agent should continuously check for updates.
• Use the Publisher as a proxy for conflict detection (described as First to Publisher Wins).
• The subscription is a client subscription type.

1. Test that replication is working for this subscription. For example, by changing a value in one of the user-defined tables (table names for user-defined tables always end with an underscore).
   
2. Set the Merge Agent to run at a one-second polling interval, or at the desired frequency.
   
3. Validate the subscription(s) to check that there are no discrepancies between the data at the Publisher and Subscriber(s). For example, use the Validate All Subscriptions dialog, selecting the option to use both the checksum and rowcount validation methods. See the Microsoft SQL Server documentation for further information.
   
4. Back up the database(s). See:
   
• The Administration Center document Creating and Maintaining Databases, for information on backing up iBase connection files
• Microsoft SQL Server documentation for information on backing up the replicated SQL Server databases
  
5. Tell the iBase administrator(s) that replication is reconfigured at the Subscriber(s).