This is a problem that usually arises due to poor program design and not because of the database administrator. The problem is summarized in that two sessions are holding each other, leaving them both suspended. After a few seconds, one of the sessions will detect that there is a deadlock and will roll back its operation, thus releasing the lock and allowing the other session to continue its work.

Naturally, this problem is often caused by a design flaw in the program. An example of this scenario is when two sessions are attempting to modify a specific field, and this modification in both sessions depends on a value from the other session, leaving both sessions blocked.

The database administrator does not intervene in such a scenario; rather, the solution is handled automatically by Oracle.