Qlik Replicate task error: Can't resume task after replication slot was dropped

[Steve_Nguyen]

A Qlik Replicate task errors out with:

 [SOURCE_CAPTURE  ]E:  Can't resume task after replication slot was dropped. 

This error may occur if PostgreSQL has moved from a primary to a secondary node (or vice versa), leading to the slot being lost.

It may also occur if PostgreSQL was recently upgraded. 

Resolution

If PostgreSQL has switched nodes, the slot will be lost. Unless your database admin is able to sync up the replication slots, a new slot will need to be created or the target needs to be reloaded.

If a new slot has been created, we can use an internal parameter, set the slot name, and resume the task without a full reload:

1. Open the Qlik Replicate console
2. Locate your PostgreSQL endpoint
3. Switch to Advanced 
4. Add the following Internal Parameter: slotName 
   Use the new Slot Name (provided by your DBA) as the value. 
   
   For more information on how to add Internal Parameters, see: Qlik Replicate: How to set Internal Parameters and what are they for? 

Environment

Qlik Replicate 

[SK2]

@Steve_Nguyen  - Can you pls advise how to recreate the slot with same name/LSN.