Oracle has the log miner tool, but that will only work on an Oracle database. Also, it is reading the redo logs, so that would be a transaction that is committed. You would basically get the same error as you have here. This is not mentioning the fact that you would have to first port this application over to Oracle (assuming it is supported) and then wait for the error to occur before being able to test it.

I would not say that there is no solution. You have plenty of solutions in SQL Server to consider such as:

- Setting up a trace to monitor activity/statements and capture the offending statement

- Setup a DML trigger to capture the data you want and to report it back to you

- Possibly setup an Extended Event to do what you are looking for. I have little knowledge with Extended Events though, so I am unsure if it would be able to do what you are looking for

- Setup database auditing

If it is an important matter to your business it is worth researching more before declaring that it cannot be done.

My two cents.