experiences with stgrule for replication


Oct 23, 2017
Reaction score
We are doing a HW refresh and also changing the OS which we are running our instances on.

Since v8.1.13 they have added a new feature for replication through stgrules. [1]

Currently we are running v8.1.14.200 and have started to use this stgrule and planned also to do cleanup of SDRC table afterwards. [2]

Perhaps not so surprisingly (since it is a new feature relative to the version we are running) we are facing several issues with this; to name a few - we cannot cancel it, sessions seem to be hanging on source side if we restart target server and having to restart instances constantly to cancel the process.

Also now after a case ongoing with IBM they seem to think that we might be hitting this issue - IT42566; I see there that there is a fix for that in v8.1.18.

I also see however that there are some APARs for 8.1.18 which are not fixed yet that would affect the same stgrule: IT43604 & IT43605.

So wanted to post here and ask have anyone here have started using it; if so which version are you running and what are your experiences with it? The reason I am asking that is because we have to consider doing an upgrade or perhaps going back to protect stg/replicate node.

[1] https://www.ibm.com/docs/en/spectru...eplication-by-using-replication-storage-rules
[2] https://www.ibm.com/docs/en/spectru...-reducing-database-size-by-pruning-sdrc-table