Hi there,

This relates to the following discussion: https://debezium.zulipchat.com/#narrow/channel/348250-community-oracle/topic/OldestScn.20not.20advancing.20in.203.2E2.2E1/near/536311724

In versions < 3.2.0 there was an optimisation where a transaction was only tracked once DML appeared. This caused issues with e.g. the UserName.

Resolving this has had a side-effect for us where sometimes transactions will be started (we think this is done during certain operations in SQL developer) that are not committed for a very long period of time. Because we alert based on the oldest_scn age to our standby this creates scenarios where we have to request DBAs to kill these orphaned transactions

Debezium already allows for abandonment of long running transactions using e.g. log.mining.transaction.retention.ms. What would be helpful for us would be to have a signal to accomplish the same thing where we can establish our own set of rules on when to abandon a particular transaction and then use a signal to achieve that.