ORA-08179: concurrency check failed

Question

I'm getting the error 'ORA-08179: concurrency check failed' when calling UpdateAll on a Typed Dataset using ODP.Net 2.112.1.2 connecting to an Oracle 11.1.0.6 database.
The only information about this error I can find is something about an optimistic locking problem with an OCI call.
What the code is doing is fairly complicated, the summary is:
There is one large Typed Dataset that has been setup to use a single permanent Oracle connection.
Various datatables are populated initially.
More data tables are populated after user selections.
Create a transaction (and keep it for the duration of the lock), and refresh a single row in one table using FOR UPDATE to lock it and the related tables are re-filled.
I then make changes to one of the data tables using the UI, commit the transaction to release the lock (and then dispose of it), then call UpdateAll to run the update statement on the changed data table. At this point I get the Oracle error.
I'm not sure how I could get an optimistic locking error when I'm the only person using this database and I'm only using a single Oracle transaction.
I can't see any information about this anywhere so any help would be greatly appreciated.
Thanks,
John.

Answer 1

I've finally managed to get to the bottom of this.
If you use batch updates with an ODP.Net Data Adapter and use a stored PL/SQL procedure to perform the update then you have to make sure that the last SQL statement executed affects at least one row. Otherwise it thinks that the update has failed because of an optimistic concurrency error (ORA-08179).
I would prefer it if you could just return the rows affected either using a parameter or a function return value instead of it using the same mechanism as a simple Update command. Either that or just don't bother and let the stored procedure detect and raise the concurrency error. At the very least it should document this restriction somewhere.
John.