The hang is caused by an exclusive row lock on table EMPLOYEE.
挂起是由表 EMPLOYEE上一个独占式的行锁导致的。
That lock is the row lock that is associated with the row being exported.
该锁是与正在被导出的行相关联的行锁。
This is because the new X row lock and the is table lock are not compatible.
这是因为新的x行锁定和is表锁定是不兼容的。
All back rise seams should be two-thread chain stitch or double row lock stitch.
所有后档缝应当用双针链式缝迹或双行锁式线迹。
The row is formatted in the target page and an X (exclusive) row lock is obtained on it.
在目标页中对该行进行格式化，并获得该行上的一个X（exclusive，独占的）行锁。
The LOCK TABLE command can be used to lock a table instead of using the default row locking.
可使用LOCKTABLE命令来锁定一个表，而不是使用缺省的行锁定。
G stands for "granted" and means that the transaction with transaction handle 2 owns the row lock.
g代表“granted”，意即事务句柄为2的事务拥有行锁。
After some small number of row locks are obtained, a lock escalation to a table lock will occur automatically.
当获得少量的行锁时，行锁就会自动地逐渐升级为表锁。
If a transaction obtains a row lock for a row, the transaction also acquires a table lock for the corresponding table.
如果一个事务获得了一行的行锁，那么这个事务同时获得了相关的表的锁。
If this row lock is protecting an uncommitted UPDATE or DELETE action, DB2 cannot process or ignore the row until the outcome of the change is known.
如果这个行锁在保护一个未提交的UPDATE或DELETE动作，那么DB 2不能处理或忽略该行，直到变化的结果已知。
The database manager determines which locks to escalate by looking through the lock list for the application and finding the table with the most row locks.
数据库管理器通过查看应用程序的锁列表并查找行锁最多的表，来决定对哪些锁进行升级。
When DB2 performs an index or table scan, DB2 will block on a row lock when it comes across an uncommitted row which another transaction has exclusively (X) locked.
DB2在执行索引或表扫描时，如果遇到一个被另一个事务独占 (X) 锁定的未提交行，那么 DB2将阻塞在行锁上。
If a concurrently connected application happens to be holding an incompatible row lock, the import utility pauses until that application commits or rolls back its transaction.
如果一个并发连接的应用程序碰巧持有不兼容的行锁，那么import工具就会暂停，直到该应用程序提交或回滚其事务。
These next key locks are only obtained when the key INSERT finds that a scanner with a Repeatable Read (RR) isolation level has a row lock on the next-higher key in the index.
这些nextkey锁只有在keyINSERT发现带有RepeatableRead (RR)隔离级别的扫描器在索引中的next -higher键上有一个行锁时才能获得。
Shortages in the lock maintenance space can lead to so-called lock escalations, in which row locks are escalated to undesirable table locks, which can even lead to deadlock situations.
锁维护空间不足可能会导致所谓的“锁提升”，其中，行锁被提升为不必要的表锁，这甚至可能会导致死锁情况。
Each row in the chart refers to a different lock.
图表中的每一行指的是一个不同的锁。
Why does DB2 lock this table, row, or object?
为什么DB 2锁住了这个表、行或者对象？
Another special case of locking is the need to lock something where currently no database row exists.
锁定的另一个特例是需要锁定当前数据库行中不存在的项目。
The only alternative to a lock on every new row is a table lock (since there are no page locks in DB2).
对于每个新行之上的锁，惟一可以替代的是表锁(DB 2中没有页锁)。
Transaction 1 reads a specific record and places a lock on that row.
事务1读取某条特定记录并对该行应用一个锁。
In this case, a logical lock (not a physical database lock) is used to flag that a row is in use for a long-term duration.
在本方案中，通过逻辑锁(而不是物理锁)来对在较长时间中使用的数据行进行标记。
And the location of every row is in a fixed location, allowing for techniques such as lock escalation when too many fine-grained locks would otherwise be needed.
并且由于每一行都被存储在固定的位置，使得锁升级这样的技术得以实现，以避免过多细粒度锁。
If the MDB locks resources transactionally (for example, it may lock a database row), these resources will not become unlocked until the end of the batch.
如果MD b以事务的方式锁定资源(例如，它可以锁定数据库行)，则在批结束之前，这些资源将保持锁定。
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的部门行设置独占锁。
Within the child thread, open a new connection to DB2 and fetch a row from the lock table for the requested resource ID.
在子线程中，打开新的DB 2连接，在锁表中获取具有所请求的资源ID的一行。
These locks could be table level, row level, or lock on index, and so on.
这些锁可以是表级锁、行级锁、索引锁等等。
In the meantime, transaction 2 wants access to that same row, but it has to wait until the lock is released by transaction 1.
同时，事务2希望访问这个行，但是它必须等待事务1释放该行的锁。
This causes DB2 to use a table lock for all subsequent SQL statements using the table, until the locksize is changed back to ROW.
这将导致DB 2为随后使用该表的所有sql语句使用一个表锁，直到locksize参数改回到ROW。
Agent 2: NS lock WAITING on main table row ID (0; a) (from select).
代理2：ns锁对于主表行(0；a)为WAITING(由于select)。
Agent 2: NS lock GRANTED on child table row ID (0.4) (from select).
代理2：ns锁对子表行ID(0.4)为GRANTED(由于select)。
应用推荐