Within‑Transaction Integrity Issues
“Between‑Transaction Integrity Issues” on page 658 describes the integrity risks presented by concurrent updating of a table by different transactions. This topic describes the risks associated with cursor conflicts that occur within an individual transaction.
Cursor conflicts occur in the following situations:
All three of these updates are dirty because the same row was updated twice without the transaction having been committed.
Note that the system permits all three of the dirty updates to occur and then returns a cursor conflict warning to the requesting program. Resolution of the integrity breach is left to the user.
Because of the multiple possible integrity risks associated with declaring and opening multiple cursors within the same transaction, you should code your applications so those risks cannot occur.