This content has been marked as final. Show 2 replies
This is a strange one. That error should only occur when you are using RETURN TWOSAFE replication. It doesn't look like you are but maybe you can confirm if that is the case or not. I think you need to open an SR on this as if you are not using RETURN TWOSAFE then this is likely a bug. Even if you are using RETURN TWOSAFE I don't see any reason why the error would suddenly occur in the scenario you describe so again at the moment I am thinking this may be a bug. In any event in depth diagnosis is needed to figure out what is happening here and an SR is the best vehicle for that.
Note that 220.127.116.11.0 is an extremely old release so you might want to try upgrading to a more recent 7.0 release in case the problem was fixed already. Of course 7.0 itself is very old so better still, maybe consider upgrading to 11.2.2 :-)