Update agent - Precisely Data Integrity Suite

1. Go 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 are upgrading to includes an IBM i installation library update. If not, you can skip this step.
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> --version=<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 Suite service version.
• <previous_version>: replace with the stable previous version to roll back to.

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

• Action: Update Suite 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 Suite 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 there are 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.

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 Db2 LUW Runtime Client version 11 or later provided by IBM onto the agent machine. The file is typically named <version>_<os>_rtcl.tar.gz.
2. Untar the file to /precisely/connect/cdc/uploads.
3. Run the following command and follow the prompts shown:

   kubectl exec -it -n <your project pod namespace> <your project pod> -- /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:

   cp /precisely/connect/cdc/sqllib/java/db2jcc4.jar /precisely/connect/cdc/drivers/db2/

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

Update operator

Manually update the operator version by updating the CLI and applying the desired version using the following commands:

1. Update the CLI by executing this command: ./discli updateCli
2. The operator version updates automatically. However, if an issue arises or you need to use a specific operator version, you can update it manually by running this command: ./discli agent applyOperatorVersion <operator_version_number>.

Update Kafka

To upgrade Kafka from version 1.1.0 to 1.1.2, a manual update is required. For all other versions, the update process is automated.

Prerequisite: Before proceeding with updates, ensure that the workload is stopped. This suspension is necessary to prevent data inconsistency and ensure a smooth maintenance process.

1. Before updating the Kafka version, ensure you have updated the data integration services as described above.
2. Update the CLI by executing this command: ./discli updateCli
3. Stop the agent by running this command: ./discli agent stop
4. Apply the Kafka version by executing this command: ./discli agent applyKafkaVersion 1.1.2
5. Start the agent by running the command: ./discli agent start
6. Ensure that the agent is healthy, operational, and running as expected.
7. Once the agent is confirmed to be healthy, start all the workloads.