Update agent - Precisely Data Integrity Suite

Data Integrity Suite
Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2026

When an Update label appears next to an agent name, it indicates that an update is available for that specific agent used in data replication processes. To update the services on the agent:

  1. Navigate to Configuration > Agents.
  2. Select the agent with the Update label. This will open the side panel, which lists the services with available updates for you to install.
  3. Before performing the update, ensure the environment is prepared. Stop all running pipelines, stop the runtime engine, stop the capture agents, and stop the log readers. This step is critical to prevent data transfer during the update and to ensure consistency.
  4. Install the new change selector library on the IBM i server when upgrading Connect-CDC.
    • First, verify the version of the installation library.
    • If installing to a new library, update the data connections to reference the new install library name. This value is specified in the Data Connection configuration.
    • After updating the library reference, ensure you apply the configuration changes later in the process.
    Note: This step is only necessary if the Connect CDC version you're upgrading to includes an IBM i installation library update. If not, this step can be skipped.
  5. To perform the service update, switch to the directory where the agent is installed (i.e., where the discli file is located) and run the following command: ./discli agent update <service name> <target version>

Prerequisites

  • Tool:discli installed and updated to the latest release before running updates.
  • Kubernetes access: kubectl configured for the target cluster and namespace access.

Placeholders

  • <latest_version>: replace with the target latest DIS service version.
  • <previous_version>: replace with the stable previous version to roll back to.

Case 1: Agent installed with 2.0.xx (no DIS services updated yet)

  • Action: Update DIS services directly to latest.
  • Commands:
    • ./discli agent update connect-cdc --version=<latest_version>
    • ./discli agent update connect-hub --version=<latest_version>
    • ./discli agent update cloud-applier --version=<latest_version>
    • ./discli agent update sqdata-management --version=<latest_version>

Case 2: Agent installed with 2.1.xx (before 2.1.5) and one or more DIS services already updated (engine verification issues)

  • Step 1: Roll back services to a previous stable version:
    • ./discli agent update connect-cdc --version=<previous_version>
    • ./discli agent update connect-hub --version=<previous_version>
    • ./discli agent update cloud-applier --version=<previous_version>
    • ./discli agent update sqdata-management --version=<previous_version>
  • Step 2: Delete existing secrets:
    • kubectl delete secret connect-nacl-key-secret -n precisely-connect-cdc-ns
    • kubectl delete secret connect-nacl-key-secret -n precisely-sqdata-management-ns
    • kubectl delete secret connect-agent-secret -n precisely-connect-cdc-ns
    • kubectl delete secret connect-agent-secret -n precisely-connect-hub-ns
    • kubectl delete secret connect-agent-secret -n precisely-cloud-applier-ns
    • kubectl delete secret connect-agent-secret -n precisely-sqdata-management-ns
  • Step 3: Update services again to latest:
    • ./discli agent update connect-cdc --version=<latest_version>
    • ./discli agent update connect-hub --version=<latest_version>
    • ./discli agent update cloud-applier --version=<latest_version>
    • ./discli agent update sqdata-management --version=<latest_version>

Case 3: Agent installed with 2.1.5

  • Action: Same as Case 1 (if no engine verification issues) — update to latest:
  • ./discli agent update connect-cdc --version=<latest_version>
  • ./discli agent update connect-hub --version=<latest_version>
  • ./discli agent update cloud-applier --version=<latest_version>
  • ./discli agent update sqdata-management --version=<latest_version>
If you encounter engine verification issues after any update: follow Case 2 rollback → delete secrets → re-update.
Table 1. Agent services and their latest target version
Service Name Previous Target Version Latest Target Version Command Release Date
connect-cdc 6.0.0901 6.0.0903 ./discli agent update connect-cdc --version=6.0.0903 March 2026
connect-hub 1.15.2 1.15.4 ./discli agent update connect-hub --version=1.15.4 March 2026
cloud-applier 1.14.0 1.14.2 ./discli agent update cloud-applier --version=1.14.2 March 2026
sqdata-management 2.5.2 2.5.3 ./discli agent update sqdata-management --version=2.5.3 March 2026

Db2 LUW Runtime Client installation

The following steps must be performed if you want to replicate from Db2 LUW sources for a continuous replication pipeline:

  1. Download the latest Db2 LUW Runtime Client provided by IBM onto your agent's machine.
  2. Untar the file to /precisely/connect/cdc/uploads
  3. Run the following command and follow the user prompts shown:

    kubectl exec -it -n precisely-connect-cdc-ns connect-cdc-0 -- /usr/bin/sh -c "/var/precisely/di/uploads/rtcl/db2_install -f sysreq"

  4. If you have not yet added the db2jcc4.jar driver to the drivers path, perform the following command:

    kubectl exec -it -n precisely-connect-cdc-ns connect-cdc-0 -- /usr/bin/sh -c "cp /home/connect/sqllib/java/db2jcc4.jar /opt/precisely/di/drivers/db2/"

    Note: You only need to restart the container if you perform this step.