行锁定，具有到表锁的升级。
减少锁管理器的hash表中对行和表锁的虚假锁竞争。
Reduction in false lock contentions for row and table locks in the lock manager's hash table
如果知道独占访问不会导致问题，那么就应该尽量使用表锁。
If you know that exclusive access will not cause problems, by all means use table locking.
上述比较表明，使用表锁而不是行锁可以节省大约3%的耗时。
The above comparison shows that causing table locks to be used instead of row locks saved about 3% in elapsed time.
对于每个新行之上的锁，惟一可以替代的是表锁(DB 2中没有页锁)。
The only alternative to a lock on every new row is a table lock (since there are no page locks in DB2).
如果用一个表锁替换这些行锁，将不再会超出maxlocks值，那么锁升级就会停止。
If after replacing these with a single table lock, the MAXLOCKS value is no longer exceeded, lock escalation stops.
另外，应用程序间可能会发生更多死锁(因为它们都等待数量有限的表锁)，这会导致事务被回滚。
Additionally, there may be more deadlocks between applications (because they are all waiting on a limited number of table locks), which will result in transactions being rolled back.
锁维护空间不足可能会导致所谓的“锁提升”，其中，行锁被提升为不必要的表锁，这甚至可能会导致死锁情况。
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.
这将导致DB 2为随后使用该表的所有sql语句使用一个表锁，直到locksize参数改回到ROW。
This causes DB2 to use a table lock for all subsequent SQL statements using the table, until the locksize is changed back to ROW.
因为获得的锁不会跨事务边界存在，所以import工具将失去它的IX表锁，并且必须在每次提交之后请求另一个锁。
Because the acquired lock does not persist across transaction boundaries, the import utility loses its IX table lock and must request another lock after each commit.
从页面级锁升级到表级锁。
支持表级和行级锁。
并发控制支持表级和行级锁。
锁表中一个资源的行数决定了可以同时访问这个资源的最大应用程序数量。
The maximum number of applications allowed to access a resource concurrently is defined by the number of rows for this resource in the lock table.
在子线程中，打开新的DB 2连接，在锁表中获取具有所请求的资源ID的一行。
Within the child thread, open a new connection to DB2 and fetch a row from the lock table for the requested resource ID.
大容量更新锁：在向表进行大容量数据复制且指定了TABLOCK提示时使用。
Bulk Update Locks: Used when bulk-copying data into a table and the TABLOCK hint is specified.
还可以使用其他命令解压表、控制压缩期间的锁和显示节省的空间量。
There are other commands that can be used to uncompress tables, control locking while compressing, and to display space savings.
当扫描一个mdc表时，对于索引扫描，块锁可以推迟。
When scanning an MDC table, block locking could be deferred for an index scan.
架构锁：在执行依赖于表架构的操作时使用。
Schema Locks: Used when an operation dependent on the schema of a table is executing.
挂起是由表EMPLOYEE上一个独占式的行锁导致的。
The hang is caused by an exclusive row lock on table EMPLOYEE.
这说明，在创建或删除函数索引时，执行索引的表中始终持有一个排他锁。
This means that an exclusive lock is always placed on the indexed table while a functional index is being created or dropped.
它还可用于长时间的会话锁，但需要进行清理以避免表过度增长。
It can also be used for longer-lived session locks, but cleanup needs to be addressed to prevent table growth.
现在我们已经准备就绪，可以从newstaff表导出数据，并同步捕获数据库锁快照了。
We are now ready to export the data from the NEWSTAFF table, and to simultaneously capture a database lock snapshot.
在使用ONLINE关键字时，DDL操作是在没有将排它锁应用于定义特定索引表的情况下执行的。
When you use the ONLINE keyword, DDL operations execute without applying an exclusive lock to the table on which the specified index is defined.
IDS允许应用程序开发人员将锁放在不同的对象上，如数据库、表、页或行、以及索引。
IDS allows application developers to place locks on different objects, like databases, tables, pages or rows, and indexes.
对于mdc表，选择BLOCKINSERT可以提高INSERT操作的性能，因为使用的是块级的锁，避免了为INSERT操作使用行锁。
For MDC tables, the selection of BLOCKINSERT may improve the performance of INSERT operations by locking at the block level and avoiding row locks for INSERT operations.
如果不需要保留所收集的锁事件数据用作将来的分析，必须使用DROPtable语句手动删除非格式化事件表，如清单22所示。
If the collected lock event data should not be kept for further analysis purposes, the unformatted event table must be dropped manually using the drop table statement, as shown in Listing 22.
消息引擎持有独占锁的结果在于，数据库维护实用工具无法以首选的方式运行，该方式旨在对数据库中的所有表进行维护。
The result of the messaging engine holding an exclusive lock was that the database maintenance utilities could not be run in the preferred manner, which was to do so for all tables in the database.
在导出操作期间，行级别锁定应用于导出表(exportingtable)，这意味着一次只持有一个锁。
During an export operation, row-level locking is applied to the exporting table, which means that only one lock is held at a time.
应用推荐