无法为具体化视图获取应用程序锁。
An application lock could not be acquired for materializing views.
如果设备丢失，消费者可以得到自己的手机，当检测到新的SIM卡背面，此应用程序锁的手机。
If the device is lost, consumers can get their mobile phone back Upon detecting new SIM, this application locks phone.
该参数定义数据库管理器执行升级之前必须填入的应用程序所占有锁列表的百分比。
This parameter defines a percentage of the lock list held by an application that must be filled before the database manager performs escalation.
您可能会乐观地假设所以应用程序都使用合作锁。
Optimistically, you might assume that all of the applications will follow the cooperative locking sequence.
在一个锁关键型应用程序中，多个线程在相同的锁上争用。
A lock-bound application is one in which multiple threads are fighting over the same locks.
LOCKTIMEOUT指定了应用程序为获取锁所等待的秒数。
LOCKTIMEOUT specifies the number of seconds that an application will wait to obtain a lock.
例如，清单7中的接口定义用于配置应用程序的文件锁的字段。
For example, the interface in Listing 7 defines fields for configuring an application's file locks.
MQ应用程序没有锁，可并行运行。 此外，它可在多个线程、内核和主机盒之间弹性伸缩。
0MQ applications are concurrent without locks, and elastic over any number of threads, cores, and boxes.
在这种情形中，如果请求时没有可用的锁，那么应用程序立刻会接收到- 911。
In this situation, if no lock is available at the time of the request, the application immediately receives a -911.
使用另一个应用程序，还可以查看身份验证id、应用程序名称和锁模式等信息。
As with the other application, you can see information about the authentication ID, the application name, and the lock mode.
有一种简单可靠的解决方案模式可用于在应用程序级别实现会话锁。
A simple and reliable solution pattern can be used to implement session locking on the application level.
当表持有z锁时，任何并发应用程序都不能读取和更新该表中的数据。
When a table holds a Z lock, no concurrent application can read or update data in that table.
锁升级、锁超时和死锁将表明系统或应用程序中存在某些潜在问题。
The lock escalations, lock timeouts and deadlocks will indicate some potential problems in your system or application.
有了这一类型的锁，并发应用程序就可以读或写已锁定的表。
With this type of lock, concurrent applications can read from or write to the locked table.
在这种情形中，应用程序将等待获取锁(如果请求时没有可用的锁)，一直到被授予了锁或出现死锁为止。
In this situation, the application will wait for a lock (if one is not available at the time of the request) until either the lock is granted or until a deadlock occurs.
IDS允许应用程序开发人员将锁放在不同的对象上，如数据库、表、页或行、以及索引。
IDS allows application developers to place locks on different objects, like databases, tables, pages or rows, and indexes.
应用程序其他部分(例如锁)的配置所发生的变化不会导致日志被重新配置。
Changes to the configuration of other parts of the application (locking, for example) will not cause the logs to be reconfigured.
当任何一个应用程序所持有的锁数量达到整个锁列表大小的这个百分比时，对该应用程序所持有的锁进行锁升级。
When the number of locks held by any one application reaches this percentage of the total lock list size, lock escalation occurs for the locks held by that application.
由于employee表中的所有行都被第一个事务独占锁定，第二个应用程序进入了锁等待模式。
As all rows in the EMPLOYEE table are X-locked by the first transaction, the second application goes into lock wait mode.
每个数据库都有一个锁列表，锁列表包含了并发连接到该数据库的所有应用程序所持有的锁。
There is one lock list per database, and it contains the locks held by all applications concurrently connected to the database.
数据库管理器通过查看应用程序的锁列表并查找行锁最多的表，来决定对哪些锁进行升级。
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.
锁将资源与应用程序(叫做锁拥有者)相关联，以控制其他应用程序对同一资源的访问。
A lock associates the resource with an application, called the lock owner, to control how other applications can access the same resource.
MAXLOCKS定义了应用程序持有的锁列表的百分比，在数据库管理器执行锁升级之前必须填充该锁列表。
MAXLOCKS defines a percentage of the lock list held by an application that must be filled before the database manager performs lock escalation.
当表持有IX锁时，锁拥有者和并发应用程序可以读和更新该表中的数据。
When a table holds an IX lock, the lock owner and concurrent applications can read and update data in that table.
持有锁的事务属于用户A执行的一个应用程序。 而用户B 的事务正在等待那个锁。
The transaction owning the lock belongs to an application executed by user A. The transaction of user B is waiting on that lock.
另外，授予的锁必须不受应用程序中d B2事务的影响。
Furthermore, a granted lock must not be affected by DB2 transactions within the application.
所以dba现在知道，应用程序30正持有应用程序34所等待的锁。
So the DBA now knows that application 30 is holding the lock on which application 34 is waiting.
参与锁超时事件的应用程序通用信息，如应用程序名、认证ID等等。
General information about the applications participating in the lock-timeout event, such as application name, authentication ID, and so on.
根据应用程序、锁和sql语句有关信息，可以轻松确定死锁事件的原因，如清单21所示。
Based on the information about applications, locks, and SQL statements, you can easily determine the cause of the deadlock event, as shown in Listing 21.
确定问题锁后，您应该重写应用程序来减少该锁的争用。
Once you have identified problematic locks, you should rewrite the application to reduce the contention on the lock.
应用推荐