Replica Configuration

The Replica configuration defines what data should be received from whom and how to process the received data.

Contents

Receive Groups

A receive group is a group of Masters that share a configuration and data received from them are treated in the same way.

Open Replication folder.

  1. Open Replica Configuration / Receive Group – Details. There should be at least one receive group in the navigator.
  2. Select each Replication Object and each LU and check that the attributes New_Allowed and Modify_Allowed are properly checked.
  3. Select each view and check the right pane in the window. The window contains the columns belonging to each view. All columns that are replicated from the Master have the attributes New_Allowed and Modify_Allowed checked. Make the necessary changes.

    Note! Some columns are not allowed to be part of the attribute string when a New or Modify procedure on a LU is called. These columns have to have New_Allowed or Modify_Allowed unchecked otherwise an error is reported when the replication process tries to update the database.

Creating and installing packages

When the Replication configuration for all the receive groups are finished all packages must be generated and installed on the Replica. If the background processes are running and replication data are received but the packages are not installed Connectivity will report an error.

Open the Replication folder.

  1. Open Replication Object Definitions.
    1. Select a Replication Object and press RMB.
    2. Choose Create Receive Package… on the menu.
    3. Create a package for each replication object using the package templates (Template_BOR.api and Template_BOR.apy).

Receiving replicated data

When replicated data is received the replication process will use the standard operations New and Modify (if nothing else has been configured) to update the database. A common source of error is replicated data that is not allowed to be part of the attribute string when the New or Modify operation is called. Any such column has to be excluded (Receive Groups). There is no easy way to find out which columns are not allowed. One way is to look inside the LU. The other way is to the process the message, look at the error message, uncheck the column, regenerate and reinstall the package, reprocess the message, find the next column that gives an error and so on.

Note! The only way to reprocess a Connectivity message that is in State = Rejected is to change the state of the message in SQL*Plus or any other suitable tool. Set State = Posted and the message will be reprocessed by Connectivity.

An error message can be found in the runtime monitor window.

Open the Administration folder.

  1. Open Monitoring / Database Background Jobs.
    Look for rows where State = Error and Function = Replication_Util_API.Receive_Message__. The attribute Argument will contain the Connectivity message id. The Error Text attribute will contain the error message generated by the replication process.

E.g. ITEM_BOR_API.Receive_Message.ORA-20105: ITEM.InventoryPart.ORA-20121: InventoryPart.INSERT: [COUNT_VARIANCE] may not be specified for new objects.

In this case the COUNT_VARIANCE column must have the attribute New_Allowed (Receive Groups) unchecked

E.g. ITEM_BOR_API.Receive_Message.ORA-20105: ITEM.InventoryPart.Operation NEW in conflict - record rejected.

This is not really an error. The record has been rejected because the attribute New_Modify_Error in Replication Object Definition – Overview (Creating Replication Objects Definitions) has been checked.