Note that applications that do not use this programming model are not considered optimistic locking applications, and they will continue to work as before.
For instance, if the application USES pessimistic locking, don't change the application during the migration to use optimistic locking.
Note that without DDL changes, optimistic locking applications may get more false negatives than with DDL changes.
A way to avoid this is to follow an optimistic locking strategy and assume that it is very unlikely that another user will try to change the same row that you are changing.
However, you can iterate through a set of rows and update each row individually while using optimistic locking techniques.
The use of optimistic locking offers more concurrent access to the data.
Such a column is need for optimistic locking to implement long conversion (application transaction).
Since the new SQL expressions and attributes for optimistic locking can be used with no DDL changes to the tables involved, you can easily try optimistic locking in your test applications.
As physical database locks are held for a longer time duration than with an optimistic locking strategy, there is more of a chance for performance and throughput being impacted.
A collection of SDOs that has been altered also maintains a record of its original values, enabling certain sorts of optimistic locking algorithms.