LOB lock and LOB table space lock duration

This information describes the duration of LOB locks and LOB table space locks.

The duration of LOB locks

Begin program-specific programming interface information. Locks on LOBs are taken when they are needed for an INSERT or UPDATE operations and released immediately at the completion of the operation. LOB locks are not held for SELECT and DELETE operations. In the case of an application that uses the uncommitted read option, a LOB lock might be acquired, but only to test the LOB for completeness. The lock is released immediately after it is acquired.

The duration of LOB table space locks

Locks on LOB table spaces are acquired when they are needed. When the table space lock is released is determined by a combination of factors:
  • The RELEASE option of bind.
  • Whether the SQL statement is static or dynamic.
  • Whether there are held cursors or held locators.

When the RELEASE(COMMIT) option is used, the lock is released at the next commit point, unless there are held cursors or held locators. If the RELEASE(DEALLOCATE) option is used, the lock is released when the object is deallocated (the application ends). The RELEASE bind option has no effect on dynamic SQL statements, which always use RELEASE(COMMIT), unless you use dynamic statement caching. End program-specific programming interface information.