Skip to main content Skip to complementary content

Prerequisites

The following section describes the prerequisites for working with the Qlik Replicate IBM DB2 for iSeries endpoint.

Information note

iAccess ODBC driver 7.1.0. is not supported.

Client

The following section explains how to install the driver required by the IBM DB2 for iSeries endpoint.

Replicate on Windows

  1. Download the IBM i Access Client Solutions Windows Application Package from the IBM website.

    For more information, see https://www.ibm.com/support/pages/ibm-i-access-client-solutions-5733xj1

  2. Install the downloaded package on the Replicate server.

    This will install the iSeries Access ODBC Driver that is used by Replicate. The version supported by Replicate is 13.64.xx.

    After the installation completes, an entry will be added to the Drivers tab in the Windows ODBC Data Source Administrator application.

    Example:

    IBM i Access ODBC Driver version 13.64.26

Information note

The displayed driver version will differ according to where you view it. For instance, assuming the driver version is as in the above example, then:

  • In the Replicate task logs, the driver will appear as ODBC driver version: '07.01.026'.
  • In the package’s readme file, the version will will appear as 5733-XJ1 Version: 1.1.0.26

Replicate on Linux

  1. Download the IBM i Access Client Solutions Linux Application Package from the IBM website.

    For more information, see https://www.ibm.com/docs/en/i/7.2?topic=packages-linux-application-package

  2. Stop the Replicate service:

    ./areplicate stop
  3. Optionally, confirm that the service has stopped:

    ./areplicate status
  4. Install the RPM that is included in the downloaded package.

    Example:

    rpm -i ibm-iaccess-1.1.0.26-1.0.x86_64

    Information note

    The displayed driver version will different in the Replicate task logs. For instance, assuming the driver version is as in the above example, it will appear as ODBC driver version: '07.01.026' in the Replicate task logs.

  5. Change the working directory to <Replicate_Install_Dir>/bin.

  6. Add the DB2 driver location to the Linux library path.

    To do this, add the following line to the site_ arep_login.sh file in <install_dir>/replicate/bin:

    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/path/lib64

    where path is the path to the driver.

    Example:

    echo "export LD_LIBRARY_PATH=\$LD_LIBRARY_PATH:/opt/ibm/iaccess/lib64" >> site_arep_login.sh

  7. Optionally, confirm that the driver location was copied:

    cat site_arep_login.sh
  8. After the installation completes, open the /etc/odbcinst.ini file and make sure it contains the following section:

    [IBM i Access ODBC Driver 64-bit]
    Description = IBM i Access for Linux 64-bit ODBC Driver Driver = /opt/ibm/iaccess/lib64/libcwbodbc.so Setup = /opt/ibm/iaccess/lib64/libcwbodbcs.so Threading = 0 DontDLClose = 1 UsageCount = 1
  9. Start the Replicate service:

    ./areplicate start
  10. Optionally, confirm that the service has started:

    ./areplicate status

Change processing

Journal prerequisites

All of the source tables for a given replication task need to be journaled to the same journal. The name of the journal and the library in which it is located must be specified in the endpoint settings. During the task, Replicate polls this journal for changes to the source tables.

When you start journaling the source tables, the Record images parameter can be set to *BOTH (for capturing before and after images) or *AFTER.

When the Record images parameter set to *AFTER. deleted records will contain NULL values in their data fields. To save a copy of the deleted record to the deleted record journal, you must set the Record images parameter set to *BOTH.

Information note

If you need to run several replication tasks (that replicate data from IBM DB2 for iSeries), it is more efficient (though not essential) to create a separate journal for each task. As only one journal can be specified per endpoint, you would also need to define a separate endpoint for each task.

MINENTDTA parameter

The MINENTDTA parameter must be set to *NONE as *FILE (minimal logging) is not supported.

 

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!