Replicating ADALOD Data to the RDBMS Tables

#### Search Results

Search

# Replicating ADALOD Data to the RDBMS Tables

You can use the LOAD and UPDATE functions of the Adabas ADALOD utility to add and update data in the RDBMS tables. In both cases, you must specify RPLLOAD=YES when running the utility to ensure that the loaded data is automatically replicated.

The processing of ADALOD data for Event Replicator Target Adapter is the same as the processing of regularly replicated data for Event Replicator Target Adapter. In other words, the data that is loaded is processed by subscriptions; if a subscription is activated, includes a generated global format buffer field table (GFFT) for the Adabas file being loaded or updated, and includes an activated destination with a destination class type of "SAGTARG", the data is replicated and sent as an XML message to the Event Replicator Target Adapter for processing.

Before you decide to add data to the RDBMS tables using the ADALOD utility, consider the following potential problems:

- All records processed by ADALOD and sent to the Event Replicator Target Adapter with action types of "Insert" are treated by the Event Replicator Target Adapter as if they were new records, unless the RESEND flag associated with the incoming data from Event Replicator for Adabas has been set to YES. If the RESEND flag is set to YES, checks are performed to determine whether a record already exists with the same primary key. If it does, the existing row is deleted and a new one is inserted for the new incoming data.

  Note
  If, during Insert processing, the RESEND flag is set to NO and a record with the same primary key as an existing record is found in the RDBMS tables, Event Replicator Target Adapter processing will fail.

- Performance problems can occur due to the massive numbers of records that might be sent if you use the ADALOD utility and the Event Replicator Target Adapter to add records to the RDBMS tables. A single subscription activated for Event Replicator Target Adapter processing can update multiple RDBMS tables simultaneously (depending on the number of pertinent SFILE definitions and the number of different generated global format buffer field tables (GFFTs) that exist in the subscription). If multiple subscriptions are activated for Event Replicator Target Adapter processing, then, the amount of traffic on your system could be quite high.

  To limit the number of ADALOD records replicated through the Event Replicator Target Adapter, you can deactivate some of the subscriptions, use transaction filter definitions, or elect not to drop an RDBMS table prior to the ADALOD utility run (in this case, all insert transaction will fail if the primary key already exists for that table).