Allows you to have Replication Option select all records and
    fields from all user relations, excluding views, that are in
    the source database at the time the transfer is defined. If
    you wish to move views, you must use the move-views-clause or
    the MOVE RELATION clause. Fields defined with a COMPUTED_BY
    clause are restricted to those that use the value expressions
    shown in the value-expr syntax diagram in this section. If a
    field is not defined by a supported value expression, you will
    receive a warning message, and the COMPUTED_BY fields will not be
    transferred.

    If you define a transfer on a source database that is itself a
    target extraction database, do not use the MOVE RELATIONS ALL
    clause. An error will result during transfer execution because
    Replication Option will attempt to define the DDAL$VINTAGE
    relation in the new target database twice. The second transfer
    would create a DDAL$VINTAGE relation in the target database.
    Then, using the MOVE RELATIONS ALL clause, it would attempt to
    copy the DDAL$VINTAGE relation that already exists in the source
    database. To avoid this error, specify explicitly each relation
    to be moved instead of using MOVE RELATIONS ALL.

    Do not use the MOVE RELATIONS ALL statement for an extraction
    rollup transfer. If you use the MOVE RELATIONS ALL statement to
    define an extraction rollup transfer, the transfer will fail on
    execution. Instead, you must name the individual relations you
    want to transfer to the extraction rollup target.