The hang is caused by an exclusive row lock on table EMPLOYEE.
挂起是由表 EMPLOYEE上一个独占式的行锁导致的。
In the first session, execute the UPDATE statement shown in Listing 16, which places an exclusive lock on the row with department number B01.
在第一个会话中，执行清单16中的update语句，它对部门号为B01的部门行设置独占锁。
The row is formatted in the target page and an X (exclusive) row lock is obtained on it.
在目标页中对该行进行格式化，并获得该行上的一个X（exclusive，独占的）行锁。
It returns the most recently committed version of the rows, even if another concurrent session holds an exclusive row-level lock.
即使另一个并发会话持有一个独占式行级锁，它仍然返回最近提交的行。
So we can see 3 active locks: exclusive lock on key (row) level and 2 intent-exclusive locks on the page and table levels.
我们看到了3个锁信息，一个排它锁在行记录上，两个意向排它锁在页级以及数据表对象上。
So we can see 3 active locks: exclusive lock on key (row) level and 2 intent-exclusive locks on the page and table levels.
我们看到了3个锁信息，一个排它锁在行记录上，两个意向排它锁在页级以及数据表对象上。
应用推荐