Specifies that Replication Option create an extraction rollup
    database at the target site by transferring selected relations
    and fields from one or more source databases into a single
    target database. An extraction rollup database is created at the
    target site, and Replication Option reads data from the source
    databases and stores the data in a target database.

    Each time an extraction rollup transfer is executed, Replication
    Option creates a new version of the target database and
    transfers to it a complete copy of the selected records.

    The EXTRACTION ROLLUP option in the DEFINE TRANSFER statement has
    the following characteristics and limitations:

    o  Replication Option issues an error message if you do not
       enter a MOVE RELATION clause or a SELECT FIELDS list in a
       move-relations-rollup-clause.

    o  You must refer to each source database in the DEFINE TRANSFER
       statement by its database handle.

    o  On the target database, relation names and field names must
       be unique. Consequently, all target relations of the same name
       must have the same definition, and all target fields of the
       same name must have the same data type. If the definitions
       or data types differ, Replication Option issues an error
       message and the transfer fails.

    o  If any database specified in the transfer definition is on a
       node that is not available, Replication Option places the
       transfer in a waiting-to-retry state. Replication Option
       will retry the transfer at the time specified for retry in the
       schedule definition.

    o  If any of the source nodes specified in the transfer
       definition fail during the transfer, the transfer will also
       fail. Replication Option will retry the transfer at the time
       specified for retry in the schedule definition.

    o  If the transfer fails, the retry will start at the beginning,
       not where the transfer left off.

    Indexes, constraints, and access rights are not transferred
    when the target database is created. Similarly, primary key
    and foreign key attributes for a particular relation are
    not transferred because key attributes are implemented as
    constraints. Once the target database has been created, you can
    define indexes, constraints, and triggers for it and modify the
    access rights.