3542106 - How to Re-trigger Failed Partitions in Replication flow

1. Some partitions failed in replication flow and the data packages are in DHRDBMON Package overview section in "Ready State". Datasphere replication flow does not pick up these ready packets and newer packets get picked up without any issues by the working partitions.
2. The other partitions are working and are pushing delta packets without any issue. 

SAP Datasphere

1. Create a replication flow between source S/4 HANA source and Azure Data lake as target
2. There was a minor disruption in the target end and some partitions in the replication flow failed due to the target system down
3. The target system is up and replication flow works fine but there are some partitions failed in the replication flow in Datasphere 
4. In the S/4 HANA DHRDBMON transaction under Package Overview section there are some packages in ready state which does not get picked up by the Datasphere replication flow 

The data related to the packages are cached in the failed partitions in Datasphere

To move the cached data in the replication flow to the target system

• Pause the replication flow
• Resume the replication flow

Also if the replication flow has multiple objects then it is not necessary to pause the whole replication flow. In such cases select the object then choose "Object" -> "Pause Object", that way it will pause the replication for the selected object. Then choose "Object" -> "Resume Object" to resume it back. 

Pausing and Resuming a Replication Flow Run 

Pause, Resume, replication flow, package ready, limbo, cache, re-trigger, DHRDBMON , KBA , CA-DI-IS-RMS , Replication Management Service , DS-DI-RF , Replication Flows , Problem