Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
Bishnu123
Contributor II
Contributor II

New to Qlik Replicate – Help with DB2 LUW → Redshift | LSN, Recovery, Version Upgrades, Preventing Deletes & Downtime

Hi Qlik Community,

I'm new to Qlik Replicate and currently working on setting up a replication task between:

  • Source: IBM DB2 LUW
  • Target: Amazon Redshift
  • Task Mode: Full Load + Change Data Capture (CDC)

The task runs fine, but I have some questions regarding log tracking, crash recovery, version management, and CDC configuration. I’d really appreciate help from experienced users or any shared examples, steps, or links to documentation!

How to View or Track the Log Position / LSN from DB2?

  • Where can I see the last-read LSN or CDC bookmark that Qlik Replicate uses from DB2 LUW?
  • Can this be seen in the task logs, metadata tables, or via DB2 query?
  • Any sample steps or examples are very welcome.

What Happens If the Qlik Replicate Server Crashes?

  • Will tasks resume from the last known LSN/bookmark?
  • Is there a recommended recovery process or backup strategy for Qlik Replicate task metadata?
  • Can bookmarks be exported or saved externally?

Prevent Deletes in Redshift for Specific Tables Being Purged in Source

  • Some DB2 tables are purged, but we want to preserve full history in Redshift.
  • How can I configure Replicate to skip DELETE operations for specific tables?
    • Is this done via transformation rules, custom scripts, or another method?

What Happens During Unplanned DB2 Downtime?

My understanding:
If DB2 goes down, Replicate tasks with retries enabled will keep failing and resume from the last successful LSN once the system is back — assuming logs are still available.

  • Is this accurate?
  • What happens if the required log entries are gone (e.g., not retained long enough)?
    • Would we need to restart with a full load?
    • Could we restart using the last known LSN manually?

How to Prepare for Planned DB2 Downtime?

My understanding:
We can safely stop Replicate tasks before DB2 maintenance and restart them afterward.

  • Are there specific timeouts or parameters to configure?
  • Is there a best practice checklist for planned downtime?

How to Upgrade Qlik Replicate (Engine) to a New Version?

  • What is the recommended upgrade path for Qlik Replicate on Windows?
  • Do I need to back up specific folders (e.g., data, config)?
  • Will tasks and endpoints persist after upgrade?

How to Upgrade Qlik Enterprise Manager & Check Compatibility?

  • How can I upgrade Enterprise Manager alongside Replicate?
  • Is there an official compatibility matrix to match Replicate and Enterprise Manager versions?

Thanks so much in advance! Since I’m just starting out with Qlik Replicate, any examples, screenshots, best practices, or links to helpful documentation would be extremely helpful.

Best regards,

Bishnu

Labels (3)
2 Replies
OritA
Support
Support

Hi Bishnu, 

In general you can find deailed documentation about every endpoin in the Replicate Users guide. 
Source endpoints can be found under the following chapter:
https://help.qlik.com/en-US/replicate/May2025/Content/Replicate/Main/source%20endpoints/Add_manage_s...
and target endpoints can be found under the following chapter:
https://help.qlik.com/en-US/replicate/May2025/Content/Replicate/Main/target%20endpoints/Add_manage_t...
Regarding your questions. Please see below conceptual answers to your question for further details you can refer to the Replicate users guide and the answers:

How to View or Track the Log Position / LSN from DB2?

Replicate manages internally the stream position to which it reached. It does not write to the log each and evey LSN that it reads.  HOwever, if you turn Trace logging level on source_capture you may be able to see the stream position that it is reading - the LSN is part of it. 
In addition when task ends it wrties to the log the last confirmed stream position.

What Happens If the Qlik Replicate Server Crashes?

Since Replicate always manages and keeps the last confirmed stream position, if the task cashes it will try to recover from the last confirmed stream position. 

Prevent Deletes in Redshift for Specific Tables Being Purged in Source

In general, Replicate captures CDC events that are written to the db redo log. If the table purge is written to the redo log and you would like to avoid deletion of the row in the target (i.e perform logical delete) you can define transformation rule using the operation_indicator function. For furhter information please refer to the following section in the Replicate Users guide:
https://help.qlik.com/en-US/replicate/May2025/Content/Global_Common/Content/SharedEMReplicate/Custom...

 

 



 

OritA
Support
Support

Continuation of previous post:
For details about QEM product and questions please refer to the QEM users guide in the following link:
https://help.qlik.com/en-US/enterprise-manager/May2025/Content/EnterpriseManager/Main/Introduction/H...

You can also get information from articles that are posted in Qlik community:
https://community.qlik.com/t5/Official-Support-Articles/tkb-p/qlik-support-knowledge-base

and if needed you can contact your account managet and subscribe to a training and or get a PS onsite that will help you with the implementation. 

Regards,

Orit