To map a multi-member source table to consolidate data on IBM i (one-to-many)

You can use a wizard to map a lookup table and a single target table to consolidate data on IBM® i.

1. Click Configuration > Subscriptions.
2. Select a subscription, right-click and select Map Tables.
3. Select Custom Table Mapping > Consolidation One-to-many and click Next.
4. Expand the database, schema, or table from the Source Tables list to view tables from your database that are available for mapping. Right-click the database user or schema and click Refresh if you do not see your table listed.

   You may be prompted to filter databases, schemas, or tables if Automatically prompt for filter when expanding nodes is enabled in your preferences. For more information see, Setting advanced preferences. To manually define a filter, select a datastore, database, or schema and click Specify Filter.

5. Enable the table to map from the Source Table list. If you do not see your table listed, right-click the database user or schema and select Refresh.
6. If you want to hide columns so that the target is not aware of them, select a source table and click Filter Columns. Clear the check box for the column you want to hide and click OK.
7. Click Next.
8. Expand the database, schema, or table from the Target Tables list to view tables from your database that are available for mapping. Right-click the database user or schema and click Refresh if you do not see your table listed.
9. Select a table from the Target Table list. If you do not see your table listed, select the database user or schema and click Refresh. Choose one of the following options and click Next:

   Source and Target Files are Single Member

   Merges all members from the source table to a single-member target table.

   Use Source member Structure on Target

   Maintains the same multi-member structure on the target table as the one on the source table. Each source member is mapped to the corresponding target member.

   Merge Source Members into One Target Member

   Merges all members from the source table to a single member in a multi-member.

10. If you want to create a new table to map to, click Create Table.

    CDC Replication will create a table that is generally able to hold the data being sent from the source but none of the other table characteristics, such as storage options, will be specified. The tables created by CDC Replication can often be useful for quickly creating test environments. For production environments a DBA should manually create a table that will better address the expected usage of the target system. Some source data types will have no natural corresponding target data type and CDC Replication will be unable to provide a default mapping. In these cases, you will need to explicitly create the target table.

11. Check the key for the target columns and click Next.
12. Choose a replication method from the following and click Next:
    • Mirror (Change Data Capture)—Immediately replicates changes made to the source table to the target table or accumulate source table changes and replicate at a later time. If your configuration requires you to prevent recursive updates when mirroring, enable the Prevent Recursion check box. This check box is only available in components of CDC Replication that support both source and target databases.
    • Refresh (Snapshot)—Replicates a snapshot of the source table to the target table.
    • Use Relative Record Number—Enables CDC Replication to replicate updates to the target using a relative record number. When this option is checked, CDC Replication sends the Relative Record Number to the target and expects the Relative Record Number to be the identifying column on the target side. This means that the target tables cannot be updated by more than one source table (a target table cannot be a warehouse for multiple source tables). If you do not check this box, then the CDC Replication Engine for Db2® for i uses a unique key to replicate to the target.
      Notes:

      • When this option is checked, if the source table is reorganized, CDC Replication will automatically start a refresh for that table.
      • If no Relative Record Number is available on the target table (for example, if the table resides on a non-IBM i system), you can still make use of this option by mapping the Relative Record Number on the source table to a column in the target table to. For more information, see Source RRN (&CNTRRN).
      • This option is only available when you have installed the CDC Replication Engine for Db2 for i on the source database.
13. Review the mapping settings.
14. Choose one of the following options and click Finish:

    Define column mappings

    Continues with the column mapping.

    Create a new table mapping

    Allows you to start a new table mapping.

    Return to current view

    Returns you to the current view.

15. After you map your lookup table for one-to-many consolidation, set the following on the table mapping:
    1. Select the table mapping you just created in the Table Mappings view and right-click Open Mapping Details.
    2. Verify your column mappings to the target table on the Column Mappings tab. Make sure that the appropriate columns from the lookup table are mapped to the target table.
    3. Select Update all if exists from the On Insert list on the Operations tab. This ensures that CDC Replication updates all rows where the consolidation key is the same when there is an insert on the lookup table.
    4. Click Save.